Skip to content

[Bug] Should not update topic config data version while sync slave use master instead #9777

@absolute8511

Description

@absolute8511

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

Any

RocketMQ version

develop

JDK Version

Any

Describe the Bug

updateDataVersion should not be called since the slave will use the version from master. This is introduced by 46b7a98

Steps to Reproduce

start slave and wait sync, see the slave sync logs.

What Did You Expect to See?

Version should be same as master and slave sync will check the same after synced.

What Did You See Instead?

versions always not equal to the master because it is updated by slave itself

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions