Fluss Documentation add CoordinatorServer High Availability (HA) Setup - #4111
Open
striver619 wants to merge 1 commit into
Open
Fluss Documentation add CoordinatorServer High Availability (HA) Setup#4111striver619 wants to merge 1 commit into
striver619 wants to merge 1 commit into
Conversation
Author
2 tasks
leekeiabstraction
left a comment
leekeiabstraction
left a comment
Contributor
There was a problem hiding this comment.
TY for the PR. Left some comments. PTAL.
|
|
||
| After that, you have successfully deployed a distributed Fluss cluster. | ||
|
|
||
| ## Fluss CoordinatorServer High Availability (HA) Setup |
Contributor
There was a problem hiding this comment.
Can you also update upgrading.md where it says the below?
2. Currently, the Fluss `CoordinatorServer` does not yet support high availability (HA). During the `CoordinatorServer` upgrade stage, the `CoordinatorServer` will be in an unavailable state, which will affect admin operations such as table creation.
|
|
||
| :::note | ||
| During failover, admin operations (e.g., creating/dropping tables) are temporarily unavailable, | ||
| but data reads and writes on existing tables are **not** affected. The time to elect a new |
Contributor
There was a problem hiding this comment.
Data reads and writes are not affected if no tablet server fails.
|
|
||
| ```yaml | ||
| services: | ||
| coordinator-server: |
Contributor
There was a problem hiding this comment.
nit, rename this to coordinator-server-0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution Checklist
mvn clean verifypasses.(The sections below can be removed for hotfixes or typos)
-->
Purpose
This PR adds support for CoordinatorServer High Availability (HA) by providing deployment
documentation. It covers how to deploy a distributed Fluss cluster with multiple CoordinatorServers
using ZooKeeper-based leader election, ensuring failover when the primary CoordinatorServer fails.
Linked issue: close #3989
Brief change log
deploying-distributed-cluster.md— guide for deploying a distributed Fluss clusteron bare machines, including multi-CoordinatorServer HA configuration
deploying-with-docker.md— guide for deploying Fluss with Docker and Docker Compose,including multi-CoordinatorServer HA and multi-TabletServer setups
Tests
N/A — this is a documentation-only change.
API and Format
N/A — no code changes, only new documentation files.
Documentation
This PR introduces two new documentation pages: