You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Search before asking
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
The text was updated successfully, but these errors were encountered: