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

[Feature] CoordinatorServer Supports High-Available #188

Open
1 of 2 tasks
wuchong opened this issue Dec 14, 2024 · 0 comments
Open
1 of 2 tasks

[Feature] CoordinatorServer Supports High-Available #188

wuchong opened this issue Dec 14, 2024 · 0 comments
Labels
component=server feature New feature or request
Milestone

Comments

@wuchong
Copy link
Member

wuchong commented Dec 14, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

The current implementation of the CoordinatorServer in Fluss lacks high availability support, which poses a risk to system stability and reliability. Achieving high availability is crucial for ensuring that the CoordinatorServer can handle failures gracefully and continue to provide uninterrupted service to clients.

Solution

We can deploy a standby CoordinatorServer alongside the primary one. In the event of a failure in the primary CoordinatorServer, the standby server will take over the control through a leader election process orchestrated by Zookeeper. Since the CoordinatorServer is stateless, this transition is seamless and straightforward.

Anything else?

No response

Willingness to contribute

  • I'm willing to submit a PR!
@wuchong wuchong added the feature New feature or request label Dec 14, 2024
@wuchong wuchong added this to the v0.6 milestone Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component=server feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant