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 2018/09/14 01:56:08 UTC

[GitHub] yufeng629 edited a comment on issue #405: Master power off may cause consumeQueue diff from commitLog

yufeng629 edited a comment on issue #405: Master power off may cause consumeQueue diff from commitLog
URL: https://github.com/apache/rocketmq/issues/405#issuecomment-421205870
 
 
   之前提问时描述可能描述的不够好，在这里再补充下：在RocketMQ4.3.0中，消息保存到commitLog之后，并不是马上就同步数据到对应的index和comsumeQueue，而是通过另外一个服务线程ReputMessageService定时的从CommotLog同步数据到comsumeQueue，假设生产者使用同步写的方式发送了100条消息到commitLog,当ReputMessageService同步到第60条消息的时候Broker突然断电了，一段时间之后，Broker又重启了，那剩下的未同步的40条消息是否还会继续同步到comsumeQueue？？我好像并未发现源码中有这个机制，望不令赐教

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services