[
https://issues.apache.org/jira/browse/ROCKETMQ-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139886#comment-16139886
]
ASF GitHub Bot commented on ROCKETMQ-265:
-----------------------------------------
Github user vsair commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/146
LGTM, but be careful to upgrade. If the situation already happened at a
server, then upgrade to this feature, it will miss some messages. It would be
better to have some mechanism to keep consistency between consume queue and
commitlog
> when os crash for some reasons, the broker consume queue’s data maybe repeat,
> consumer can’t pull the latest message, cause message lag
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ROCKETMQ-265
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-265
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-store
> Affects Versions: 4.0.0-incubating, 4.1.0-incubating
> Reporter: yubaofu
> Assignee: yukon
> Priority: Critical
> Labels: bug
> Fix For: 4.2.0-incubating
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> when os crash for some reasons, the broker consume queue’s data maybe repeat,
> consumer can’t pull the latest message, cause message lag
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
