Skip to content

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

Open
Adi-Beker wants to merge 1 commit into
apache:developfrom
Adi-Beker:docs-dual-site-deployment
Open

docs: clarify same-city dual-site deployment considerations#10429
Adi-Beker wants to merge 1 commit into
apache:developfrom
Adi-Beker:docs-dual-site-deployment

Conversation

@Adi-Beker
Copy link
Copy Markdown

Which Issue(s) This PR Fixes

Fixes #10427

Brief Description

This PR adds a short clarification to docs/en/Deployment.md about same-city dual-site deployment considerations.

The added note highlights failure-domain planning, quorum and failover assumptions, NameServer reachability, replicated Broker groups, and avoiding unsupported active-active expectations.

How Did You Test This Change?

Documentation-only change.

Copy link
Copy Markdown

@oss-taishan-ai oss-taishan-ai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review by github-manager-bot

Summary

This PR adds documentation clarifying same-city dual-site deployment considerations to docs/en/Deployment.md.

Findings

  • [Info] docs/en/Deployment.md:5-10 — Clear and accurate guidance on failure-domain planning, quorum assumptions, and avoiding unsupported active-active expectations.
  • [Info] The content correctly emphasizes the importance of:
    • Explicit failure-domain planning
    • Quorum and failover assumptions
    • NameServer reachability from both sites
    • Using controller-based or replicated HA modes for automatic failover

Suggestions

The documentation addition is well-written and addresses a common deployment confusion. No changes needed.

Verdict

Approved — Valuable documentation improvement with accurate technical guidance.


Automated review by github-manager-bot

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

Successfully merging this pull request may close these issues.

[Doc] Clarify recommended topology for same-city dual-site RocketMQ deployments

2 participants