Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration of initial cluster state #2328

Open
Tracked by #1675
muhamadazmy opened this issue Nov 20, 2024 · 0 comments
Open
Tracked by #1675

Configuration of initial cluster state #2328

muhamadazmy opened this issue Nov 20, 2024 · 0 comments
Assignees

Comments

@muhamadazmy
Copy link
Contributor

muhamadazmy commented Nov 20, 2024

Cluster configuration life cycle

  • On startup, a ClusterController (Admin) node will seed the metadata with the initial cluster configuration. The seed configuration defaults to a single node cluster but can be overridden via the node config file.
  • If configuration already exists in metadata, no initialisation of configuration is needed and metadata becomes source of truth.
  • Developer/User can only inspect and/or reconfigure via the restatectl command (or any other grpc client)

What to configure

Cluster configuration should cover all the aspects of cluster setup and replication this includes

  • Number of partitions
  • Default Bifrost provider. (fixed to replicated ?)
  • Replication property
  • Node selector strategy
  • Scheduler strategy

Developer Experience (DX)

ClusterConfiguration will be managed by MetadataManager. This implies the cluster configuration will be versioned and watchable.

Developers interested in configuration can use the Metadata watcher mechanism to react to changes in configuration. The only prospect right now is the ClusterController (more specifically the LogsController).

Or reconfiguration, LogsController should react by potentially seal and reconfigure the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant