imzs opened a new issue, #10604: URL: https://github.com/apache/rocketmq/issues/10604
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment . ### RocketMQ version . ### JDK Version . ### Describe the Bug In TopicConfigManager#buildSerializeWrapper, when enableSplitRegistration is enabled, the DataVersion was advanced by directly calling getDataVersion().nextVersion(). Under RocksDB config storage, the version was only bumped in memory and never persisted, since RocksDBTopicConfigManager overrides updateDataVersion() to write the version into RocksDB. We should use updateDataVersion() to advance the version through the unified, overridable path so it is persisted correctly and carries the proper stateMachineVersion. ### Steps to Reproduce . ### What Did You Expect to See? . ### What Did You See Instead? . ### Additional Context . -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
