You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/03/17 12:16:43 UTC

[GitHub] [rocketmq] HScarb commented on issue #3449: [Delayed Message] Delivered asynchronously to improve the performance of delayed messages

HScarb commented on issue #3449:
URL: https://github.com/apache/rocketmq/issues/3449#issuecomment-1070851527


   > > * 可以通过配置同时支持同步和异步两种方式。
   > > * 异步投递的两个主要缺点是无法保证消息顺序和数据重复问题。
   > > * 为了避免投递失败消息丢失，可以对失败消息进行重试，重试n次失败后，阻塞停止当前level对应的线程继续投递。此时投递的offset为失败消息的offset，避免了消息丢失。但是如果服务重启可能会导致数据重复，这里通过阻塞当前level继续投递降低消息重复率。
   > 
   > 但是在重试次数超过了 maxResendNum2Blocked * 2之后，状态就会置为“SKIP”，意味着允许这条消息丢失，这样理解对么？？ 除了日志记录此消息被SKIP，是否有办法让客户端感知到消息被“SKIP”且可自主恢复，比如投递到死信队列...
   
   skip仅限于从查询延迟消息的源消息为空（查询失败）的情况，如果能查到源定时消息，会一直重试下去


-- 
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: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org