Meta tags:
description=Oxia: Scalable Metadata and Index storage;

Headings (most frequently used words):

namespace, namespaces, using, creating, new, deleting, go, java, python, node, js, cli, configuration,

Text of the page (most frequently used words):
oxia (33), #namespace (29), the (21), client (10), svc (9), namespaces (8), and (7), 6648 (7), coordinator (6), architecture (6), for (5), will (5), shards (5), configuration (5), use (4), replication (4), new (4), key (4), cli (4), localhost (4), node (4), python (4), java (4), protocol (4), keys (4), notifications (3), ephemerals (3), from (3), this (3), config (3), replicationfactor (3), initialshardcount (3), default (3), name (3), internal (3), 6649 (3), public (3), cluster (3), local (3), edit (3), kubernetes (3), creating (3), partition (3), metrics (3), features (3), documentation (3), 2026 (2), policies (2), change (2), servers (2), yaml (2), deleting (2), have (2), factor (2), create (2), using (2), can (2), different (2), page (2), light (2), storage (2), consensus (2), maelstrom (2), tla (2), safety (2), correctness (2), physical (2), logical (2), design (2), goals (2), grpc (2), api (2), schema (2), reference (2), admin (2), operations (2), security (2), bare (2), metal (2), resources (2), helm (2), deployment (2), sdks (2), versioning (2), sequence (2), secondary (2), indexes (2), sorting (2), consistency (2), model (2), migrating (2), etcd (2), getting (2), started (2), what (2), blog (2), ctrl (2), copyright, 2023, series, projects, llc, website, terms, trademark, policy, other, project, please, see, https, lfprojects, org, last, updated, july, once, removed, again, immediately, pick, instruct, remove, true, whether, should, notification, feature, enabled, notificationsenabled, number, split, description, automatically, detect, add, section, specifying, initial, shard, count, configmap, kubectl, would, stored, map, value, put, connect, oxiaclient, await, const, syncclient, oxiaclientbuilder, syncoxiaclient, withnamespace, newclient, err, when, possible, specify, used, not, provided, each, has, its, own, independent, space, set, data, application, isolate, cases, also, more, visibility, which, are, going, labeled, with, well, scroll, top, github, question, give, feedback, metadata, store, coordination, system, skip, content,

Text of the page (random words):
namespaces oxia skip to content oxia metadata store and coordination system documentation blog ctrl k ctrl k documentation what is oxia getting started migrating from zk etcd features consistency model ephemerals namespaces notifications key sorting partition keys secondary indexes sequence keys versioning client sdks go java node js python deployment kubernetes helm resources bare metal security admin operations reference cli configuration schema grpc api metrics architecture design goals logical architecture physical architecture correctness protocol safety tla maelstrom consensus coordinator oxia replication protocol storage blog light what is oxia getting started migrating from zk etcd features consistency model ephemerals namespaces notifications key sorting partition keys secondary indexes sequence keys versioning client sdks go java node js python deployment kubernetes helm resources bare metal security admin operations reference cli configuration schema grpc api metrics architecture design goals logical architecture physical architecture correctness protocol safety tla maelstrom consensus coordinator oxia replication protocol storage light on this page using a namespace creating a new namespace namespace configuration deleting a namespace question give us feedback edit this page on github scroll to top documentation features namespaces namespaces oxia can partition the data in different namespaces application can use namespaces to isolate different use cases and also have more visibility in the metrics which are going to be labeled with the namespace as well each namespace has its own independent key space and set of shards using a namespace when creating an oxia client it s possible to specify the namespace to be used if not provided the client will use the default namespace go java python node js cli go client err oxia newclient localhost 6648 oxia withnamespace my namespace java syncoxiaclient client oxiaclientbuilder create localhost 6648 namespace my namespace syncclient python client oxia client localhost 6648 namespace my namespace node js const client await oxiaclient connect localhost 6648 namespace my namespace cli oxia client namespace my namespace put my key my value creating a new namespace edit the coordinator configuration eg on kubernetes it would be stored in a config map kubectl namespace oxia edit configmap oxia coordinator add a section for my new namespace specifying the initial shard count and replication factor config yaml namespaces name default initialshardcount 3 replicationfactor 3 name my new namespace initialshardcount 5 replicationfactor 3 servers public oxia 0 oxia svc oxia svc cluster local 6648 internal oxia 0 oxia svc 6649 public oxia 1 oxia svc oxia svc cluster local 6648 internal oxia 1 oxia svc 6649 public oxia 2 oxia svc oxia svc cluster local 6648 internal oxia 2 oxia svc 6649 the oxia coordinator will automatically detect the change and will create the shards for the namespace namespace configuration name description default initialshardcount number of shards to split the namespace replicationfactor replication factor for the shards notificationsenabled whether the namespace should have notification feature enabled true deleting a namespace once the namespace is removed from the config yaml the oxia coordinator will again immediately pick up the change and will instruct the oxia servers to remove the shards for this namespace last updated on july 11 2026 ephemerals notifications copyright 2023 2026 oxia a series of lf projects llc for website terms of use trademark policy and other project policies please see https lfprojects org policies