chennaji9 opened a new pull request, #11351:
URL: https://github.com/apache/rocketmq/pull/11351
<!-- Please make sure the target branch is right. In most case, the target
branch should be `develop`. -->
### Which Issue(s) This PR Fixes
Fixes #11334
### Brief Description
The DLedger quick-start failover section (en + cn) instructed users to "kill
the process bound to port 30931" as if that node were the Leader. The Leader is
elected by DLedger at runtime and is not fixed — following the instruction can
kill a follower, and the promised leadership switch then never happens.
The instruction now builds on the page's own earlier step: first confirm the
current Leader with `mqadmin clusterList` (BID 0 = Master, as the page itself
explains), then kill that node's process, with the three configured
`listenPort`s (30911 / 30921 / 30931 for broker-n0/n1/n2 in `conf/dledger/`)
listed so the clusterList row can be mapped to a process, then re-check with
`clusterList`.
### How Did You Test This Change?
Documentation-only change, verified statically at the PR base commit:
`distribution/conf/dledger/broker-n{0,1,2}.conf` listenPorts are
30911/30921/30931; "BID 为 0 的表示 Master" is the same page's existing explanation
two paragraphs above; no other quick-start text depends on the hardcoded
30931-Leader assumption (`grep 309` in both pages).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
