Skip to content

Commit ff94b99

Browse files
Lynxhidelynx
and
lynx
authored
[ISSUE #9155] Update doc Deployment Context
Co-authored-by: lynx <[email protected]>
1 parent 208f832 commit ff94b99

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

docs/cn/Deployment.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ $ nohup sh mqbroker -n 192.168.1.1:9876 -c $ROCKETMQ_HOME/conf/2m-noslave/broker
6969
...
7070
```
7171

72-
上面显示的启动命令用于单个NameServer的情况。对于多个NameServer的集群,broker 启动命令中-n参数后面的地址列表用分号隔开,例如 192.168.1.1:9876;192.161.2:9876
72+
上面显示的启动命令用于单个NameServer的情况。对于多个NameServer的集群,broker 启动命令中-n参数后面的地址列表用分号隔开,例如 192.168.1.1:9876;192.168.1.2:9876
7373

7474
### 3 多Master多Slave模式-异步复制
7575

@@ -168,4 +168,3 @@ RocketMQ 5.0 开始支持自动主从切换的模式,可参考以下文档
168168

169169
[设计思想](controller/design.md)
170170

171-

docs/en/Deployment.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ $ nohup sh mqbroker -n 192.168.1.1:9876 -c $ROCKETMQ_HOME/conf/2m-noslave/broker
6969
...
7070
```
7171

72-
The boot command shown above is used in the case of a single NameServer.For clusters of multiple NameServer, the address list after the -n argument in the broker boot command is separated by semicolons, for example, 192.168.1.1: 9876;192.161.2: 9876.
72+
The boot command shown above is used in the case of a single NameServer.For clusters of multiple NameServer, the address list after the -n argument in the broker boot command is separated by semicolons, for example, 192.168.1.1: 9876;192.168.1.2: 9876.
7373

7474
### 3 Multiple Master And Multiple Slave Mode-Asynchronous replication
7575

0 commit comments

Comments
 (0)