You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by di...@apache.org on 2019/02/26 02:21:42 UTC
[rocketmq] branch develop updated: [RIP-9] enhance description
about the state "SLAVE_NOT_AVAILABLE" in the chinese version of
"best_practice.md" (#867)
This is an automated email from the ASF dual-hosted git repository.
dinglei pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
The following commit(s) were added to refs/heads/develop by this push:
new 79361b8 [RIP-9] enhance description about the state "SLAVE_NOT_AVAILABLE" in the chinese version of "best_practice.md" (#867)
79361b8 is described below
commit 79361b8d6e996df38c7024f6a2d1e74e17e92771
Author: 312223105 <31...@qq.com>
AuthorDate: Tue Feb 26 10:21:37 2019 +0800
[RIP-9] enhance description about the state "SLAVE_NOT_AVAILABLE" in the chinese version of "best_practice.md" (#867)
---
docs/cn/best_practice.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/cn/best_practice.md b/docs/cn/best_practice.md
index e79c81b..dd0c56d 100755
--- a/docs/cn/best_practice.md
+++ b/docs/cn/best_practice.md
@@ -38,7 +38,7 @@
- **SLAVE_NOT_AVAILABLE**
-消息发送成功，但是此时Slave不可用。此时消息已经进入Master服务器队列，只有Master服务器宕机，消息才会丢失。如果Broker服务器的角色是同步Master，即SYNC_MASTER（默认是异步Master服务器即ASYNC_MASTER），但没有配置slave Broker服务器，则将返回该状态——无Slave服务器可用。
+消息发送成功，但是此时Slave不可用。如果Broker服务器的角色是同步Master，即SYNC_MASTER（默认是异步Master服务器即ASYNC_MASTER），但没有配置slave Broker服务器，则将返回该状态——无Slave服务器可用。
### 1.2 消息发送失败处理方式