Uploaded image for project: 'Apache RocketMQ'
  1. Apache RocketMQ
  2. ROCKETMQ-270

Slave Broker can't start normally if master broker has been cleaned commit log

    Details

    • 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
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Yukon yukon
                Reporter:
                Yukon yukon
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: