This is an automated email from the ASF dual-hosted git repository.
RongtongJin pushed a commit to branch new-official-website
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/new-official-website by this
push:
new 3623c35d59 Fix DLedger documentation typo (#785)
3623c35d59 is described below
commit 3623c35d59af1dbf5770bc5dd4c869398758b681
Author: Tuer·maimaitiaili Ba <[email protected]>
AuthorDate: Thu Sep 3 15:28:41 2026 +0800
Fix DLedger documentation typo (#785)
---
.../version-5.0/06-bestPractice/05dledger.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05dledger.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05dledger.md
index 382e5d18a5..fcb716b8ca 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05dledger.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05dledger.md
@@ -125,7 +125,7 @@ Execute kill command, or call `bin/mqshutdown broker`.
Each node in RocketMQ-on-DLedger group is compatible with old Commitlog, but
Raft replicating process works on the adding message only. So, to avoid
occurring exceptions, old Commitlog must be consistent.
If old cluster deployed in Master-Slave mode, it maybe inconsistent after
shutdown. Advising use md5sum to check at least 2 recently Commitlog file, if
occur inconsistent, maintain consistent by copy.
-Although RocketMQ-on-DLedger Group can deployed with 2 nodes, it lacks
failover ability(at least 3 nodes can tolerate one node fail).
+Although RocketMQ-on-DLedger Group can be deployed with 2 nodes, it lacks
failover ability(at least 3 nodes can tolerate one node fail).
Make sure that both Master and Slave's Commitlog is consistent, then prepare 3
machines, copy old Commitlog from Master to this 3 machines(BTW, copy the
config directory).
Then, go ahead to set configurations.
