rocketmq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jinrongt...@apache.org
Subject [rocketmq] branch develop updated: [ISSUE #2459] Fix the error in best practice doc
Date Fri, 04 Dec 2020 07:10:38 GMT
This is an automated email from the ASF dual-hosted git repository.

jinrongtong 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 b69ad17  [ISSUE #2459] Fix the error in best practice doc
b69ad17 is described below

commit b69ad17e88feacfebdeb26118688d744840b3e90
Author: Jun <62043001+coder-zzzz@users.noreply.github.com>
AuthorDate: Fri Dec 4 15:10:29 2020 +0800

    [ISSUE #2459] Fix the error in best practice doc
---
 docs/cn/best_practice.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/cn/best_practice.md b/docs/cn/best_practice.md
index e4b04e0..4ad6bb2 100755
--- a/docs/cn/best_practice.md
+++ b/docs/cn/best_practice.md
@@ -45,8 +45,8 @@
 
 Producer的send方法本身支持内部重试,重试逻辑如下:
 
-- 至多重试2次(同步发送为2次,异步发送为0次)。
-- 如果发送失败,则轮转到下一个Broker。这个方法的总耗时时间不超过sendMsgTimeout设置的值,默认10s。
+- 至多重试2次。
+- 如果同步模式发送失败,则轮转到下一个Broker,如果异步模式发送失败,则只会在当前Broker进行重试。这个方法的总耗时时间不超过sendMsgTimeout设置的值,默认10s。
 - 如果本身向broker发送消息产生超时异常,就不会再重试。
 
 以上策略也是在一定程度上保证了消息可以发送成功。如果业务对消息可靠性要求比较高,建议应用增加相应的重试逻辑:比如调用send同步方法发送失败时,则尝试将消息存储到db,然后由后台线程定时重试,确保消息一定到达Broker。


Mime
View raw message