Oxia

Sharded metadata store and coordination service for distributed systems.

Provider: default
Kind: Coordination service
Category: Operations
Official docs: https://oxia-db.github.io/docs/getting-started

Properties · 3 set by this component

property	type	values	required	kind default	this component
consensus	enum	none \| raft \| paxos \| zab	no	none	inherited
managed	boolean	—	no	false	▸ false
nodes	integer	—	no	—	inherited
replicated	boolean	—	no	false	▸ true
role	enum	metadata \| lock \| discovery \| placement \| sharding \| leader-election \| config	yes	—	▸ metadata
sessionEphemeralRecords · component property	boolean	—	no	true	inherited
shardCount · component property	integer	—	no	—	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Shared dependency without redundancyerror

shared-dependency-without-redundancy

The design requires redundant discovery, but this DNS or coordination service, which everything depends on, runs on a single provider or a single replica. Its failure is the whole system's failure.

— all of these hold:
— the design requirement `availability.discoveryRedundant` is true
— any of these hold:
— the node's `redundantProviders` is false
— the node's `replicated` is false

Stateful engine pinned to a single zoneerror

stateful-engine-pinned-to-single-zone

A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.

— all of these hold:
— the node sits inside exactly 1 availability-zone group
— any of these hold:
— the node's `failover` is "none"
— the node's `replicated` is false
— the node's `replication` is "none"

Use it in a design

nodes:
  - { id: "oxia", component: "oxia" }

Other Coordination service products · 17

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Oxia: sharded metadata store and coordination system for large distributed systems, built as the
3# metadata layer for Apache Pulsar. Per the Oxia documentation a namespace is split into shards,
4# each replicated across an ensemble and served over a gRPC API.
5schemaVersion: "1"
6type: "component"
7id: "oxia"
8kind: "coordination-service"
9provider: "default"
10docs: "https://oxia-db.github.io/docs/getting-started"
11defaults:
12  role: "metadata"
13  replicated: true
14  managed: false
15properties:
16  shardCount:
17    type: "integer"
18  sessionEphemeralRecords:
19    type: "boolean"
20    default: true

The same page as markdown, for an agent: /catalogue/components/oxia.md