You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "yukon (JIRA)" <ji...@apache.org> on 2017/11/02 06:27:03 UTC

[jira] [Work started] (ROCKETMQ-270) Slave Broker can't start normally if master broker has been cleaned commit log

     [ https://issues.apache.org/jira/browse/ROCKETMQ-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ROCKETMQ-270 started by yukon.
--------------------------------------
> 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)