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/08/13 04:02:39 UTC
[GitHub] yufeng629 opened a new issue #405: Master power off may cause
consumeQueue diff from commitLog
yufeng629 opened a new issue #405: Master power off may cause consumeQueue diff from commitLog
URL: https://github.com/apache/rocketmq/issues/405
if there are some messages, all of then had flushed to commit log, but no dispatch to consumeQueue, at that moment ,the Master Broker power off, when the Master restart, those message will never dispatch to consumeQueue, because the reputFromOffset property of the ReputMessageService was set to the maxOffset of the last MappedFile when the DefaultMessageStore start
if this sitution is true, it will cause message lost
----------------------------------------------------------------
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
Re: [GitHub] yufeng629 opened a new issue #405: Master power off may
cause consumeQueue diff from commitLog
Posted by dongeforever <do...@apache.org>.
Hi yufeng629：
If the master shutdown normally, the shutdown hook will make sure all
the messages in commitlog to be dispatched.And if the master shutdown
abnormally(kill -9 or power off), the commitlog will redispatch the
messages according to the store check point.
You could check the code in CommmitLog.
Best Regards
dongeforever
2018-08-13 12:02 GMT+08:00 GitBox <gi...@apache.org>:
> yufeng629 opened a new issue #405: Master power off may cause consumeQueue
> diff from commitLog
> URL: https://github.com/apache/rocketmq/issues/405
>
>
> if there are some messages, all of then had flushed to commit log, but
> no dispatch to consumeQueue, at that moment ,the Master Broker power off,
> when the Master restart, those message will never dispatch to consumeQueue,
> because the reputFromOffset property of the ReputMessageService was set to
> the maxOffset of the last MappedFile when the DefaultMessageStore start
> 
> if this sitution is true, it will cause message lost
>
>
> ----------------------------------------------------------------
> 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
>