[
https://issues.apache.org/jira/browse/ROCKETMQ-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235277#comment-16235277
]
ASF GitHub Bot commented on ROCKETMQ-270:
-----------------------------------------
coveralls commented on issue #189: [ROCKETMQ-270] Move flush position forward
to first MappedFile whose start offset is non-zero
URL: https://github.com/apache/rocketmq/pull/189#issuecomment-341332822
[](https://coveralls.io/builds/14001009)
Coverage decreased (-0.1%) to 39.118% when pulling
**f18dc03809a36bf14f6d911a3813cf6d4f606ae2 on zhouxinyu:ROCKETMQ-270** into
**1a88fe09757969a0c8e53b8ddb793ff449aeae25 on apache:develop**.
----------------------------------------------------------------
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:
[email protected]
> Slave Broker can't start normally if master broker has been cleaned commit log
> ------------------------------------------------------------------------------
>
> Key: ROCKETMQ-270
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-270
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-broker
> Affects Versions: 4.0.0-incubating, 4.1.0-incubating
> Reporter: yukon
> Assignee: yukon
> Priority: Major
> Fix For: 4.2.0
>
>
> How to reproduce this bug?
> 1. Start master broker, and write lots of messages until broker starts
> cleaning commit log.
> 2. When the first commit log file isn't 00000000000000, start slave broker.
> In current state, slave broker will pull messages from master broker, but the
> first message's offset isn't zero, and isn't equal to commit offset, so slave
> broker could't do right flush.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
