Meta tags:
description= Oxia: Scalable Metadata and Index storage;
Headings (most frequently used words):
maelstrom,
Text of the page (most frequently used words):
#maelstrom (16), oxia (14), the (14), architecture (6), and (5), run (5), protocol (5), for (4), tla (4), this (4), partition (4), that (4), correctness (4), keys (4), coordinator (3), key (3), operations (3), nemesis (3), configuration (3), node (3), physical (3), grpc (3), documentation (3), 2026 (2), use (2), policies (2), workload (2), network (2), partitions (2), nodes (2), runs (2), build (2), lin (2), latency (2), bin (2), simulation (2), running (2), using (2), jepsen (2), system (2), light (2), benchmarks (2), storage (2), replication (2), consensus (2), safety (2), logical (2), design (2), goals (2), metrics (2), api (2), schema (2), cli (2), reference (2), admin (2), security (2), bare (2), metal (2), resources (2), helm (2), kubernetes (2), deployment (2), python (2), java (2), client (2), sdks (2), versioning (2), sequence (2), secondary (2), indexes (2), sorting (2), notifications (2), namespaces (2), ephemerals (2), consistency (2), model (2), features (2), migrating (2), from (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, checks, linearizability, concurrent, value, over, full, operation, history, while, currently, only, provides, injects, between, same, every, uniform, dist, concurrency, time, limit, path, test, you, need, download, then, will, produce, binary, make, means, can, multi, cluster, set, multiple, processes, single, machine, instead, tcp, networking, through, stdin, stdout, communicate, json, based, unlike, works, real, production, code, injecting, randomized, message, delays, verifying, external, properties, are, not, violated, library, tool, makes, easy, verify, scroll, top, edit, page, github, question, give, feedback, metadata, store, coordination, skip, content,
Text of the page (random words):
maelstrom 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 benchmarks 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 benchmarks light question give us feedback edit this page on github scroll to top documentation correctness maelstrom maelstrom maelstrom is a tool that makes it easy to run a jepsen simulation to verify the correctness of a system unlike for tla maelstrom works by running the real production code injecting network partitions and randomized message delays and verifying that the external properties are not violated using the jepsen library for oxia this means that we can run a multi node oxia cluster as a set of multiple processes running in a single physical machine instead of tcp networking through grpc we run oxia nodes that use stdin stdout to communicate using the json based maelstrom protocol to build oxia for maelstrom make maelstrom this will produce the binary in bin oxia maelstrom to run the maelstrom simulation you need to download maelstrom and then run maelstrom test w lin kv bin path to oxia maelstrom time limit 30 concurrency 2n latency 10 latency dist uniform nemesis partition the lin kv workload checks the linearizability of concurrent key value operations over the full operation history while the partition nemesis currently the only nemesis maelstrom provides injects network partitions between the oxia nodes as the workload runs this same configuration runs in ci on every build last updated on july 13 2026 tla coordinator 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
|
