Skip to content

docs: clarify same-city dual-site deployment considerations #10429

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.

Sign up for GitHub

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

Open
Adi-Beker wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

docs: clarify same-city dual-site deployment considerations #10429

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/en/Deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

## Cluster Setup

### Same-city dual-site deployment considerations

For same-city dual-site deployments, avoid treating the two sites as a simple active-active topology without explicit failure-domain planning. NameServer, Broker, and Controller components should be deployed with clear quorum and failover assumptions so that the cluster can tolerate a single-site failure without creating split-brain or unavailable write paths.

When planning this topology, place replicated Broker groups across independent failure domains, keep NameServer addresses reachable from both sites, and verify that producer and consumer clients are configured with the complete NameServer address list. If automatic failover is required, use a deployment mode that explicitly supports controller-based or replicated high-availability behavior rather than relying only on manual Broker restart or recovery.

### 1 Single Master mode

This is the simplest, but also the riskiest mode, that makes the entire service unavailable once the broker restarts or goes down. Production environments are not recommended, but it can be used for local testing and development. Here are the steps to build.
Expand Down
Loading