Skip to content

[ISSUE #11334] fix(docs): identify the DLedger leader via clusterList before failover #11351

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
chennaji9 wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

[ISSUE #11334] fix(docs): identify the DLedger leader via clusterList before failover #11351

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion docs/cn/dledger/quick_start.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ $ sh bin/dledger/fast-try.sh stop

### 3. 容灾切换

部署成功，杀掉 Leader 之后（在上面的例子中，杀掉端口 30931 所在的进程），等待约 10s 左右，用 clusterList 命令查看集群，就会发现 Leader 切换到另一个节点了。
部署成功后，先用 clusterList 命令确认当前 Leader 所在的节点（BID 为 0 的表示 Master），再杀掉该 Leader 进程（conf/dledger 中 broker-n0、broker-n1、broker-n2 的 listenPort 分别为 30911、30921、30931，Leader 由 DLedger 选举产生，并不固定是哪一个）。等待约 10s 左右，再次用 clusterList 命令查看集群，就会发现 Leader 切换到另一个节点了。



Expand Down
2 changes: 1 addition & 1 deletion docs/en/dledger/quick_start.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Quick deployment, default configuration is in directory conf/dledger, default st

### 3. Failover

After successful deployment, kill Leader process(as the above example, kill process that binds port 30931), about 10 seconds elapses, use clusterList command check cluster's status, Leader switch to another node.
After successful deployment, first use clusterList to confirm which node is the current Leader (the entry with BID 0 is the Master), then kill that Leader process (the listenPort of broker-n0, broker-n1 and broker-n2 in conf/dledger is 30911, 30921 and 30931 respectively; the Leader is elected by DLedger and is not fixed). About 10 seconds later, check the cluster's status with clusterList again, the Leader should have switched to another node.



Expand Down
Loading