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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0-incubating, 4.1.0-incubating
• Fix Version/s: 4.2.0
• Component/s: rocketmq-broker
• Assignee: Xinyu Zhou
• Reporter: Xinyu Zhou
• Created: 18/Aug/17 15:10
• Updated: 13/Dec/17 09:26
• Resolved: 13/Dec/17 09:25

Description

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.

Issue Links

• links to: GitHub Pull Request #189