[ 
https://issues.apache.org/jira/browse/ROCKETMQ-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137792#comment-16137792
 ] 

ASF GitHub Bot commented on ROCKETMQ-265:
-----------------------------------------

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/146
  
    
    [![Coverage 
Status](https://coveralls.io/builds/12948708/badge)](https://coveralls.io/builds/12948708)
    
    Coverage decreased (-0.3%) to 38.479% when pulling 
**e2a282dbd1ef95a0853607c34a1bed8808526560 on fuyou001:ROCKETMQ-265** into 
**2ddb744b3157604ec87a82143c3100728589c6ec on apache:master**.



> 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)

Reply via email to