How does oxia deal with dynamic reconfiguration?

[benjumanji]

Currently I can run zookeeper on bare metal and use the dynamic reconfiguration feature to rotate the cluster. Does oxia support the same thing? The details aren't important but roughly zookeeper site behind a single address which pulsar / bookkeeper use to address it, and the internal addresses don't matter / are dynamically learnt by the cluster using the configuration apis.

[mattisonchao]

Hi @benjumanji,

Yes. Oxia has its own membership discovery mechanism, which automatically detects changes in cluster membership. It also supports dynamically adding and decommissioning data servers.

Oxia provides two approaches for managing cluster changes:

• Declarative configuration: Users maintain the desired cluster state in a resource such as a ConfigMap or YAML file, allowing it to integrate with GitOps or other management systems.
• Management API: The Oxia Coordinator exposes endpoints for performing CRUD operations on cluster resources. The cluster automatically reconciles its actual state with the desired state.

When the cluster configuration changes, the Coordinator publishes updated shard assignments to clients, and the clients automatically refresh their shard discovery and routing information.

Does this match the scenario you had in mind? If not, could you provide a more concrete example of the node-rotation workflow you expect?