Inconsistent Broker data retrieved from different RocketMQ NameServers. #227
Comments
shangjin92
changed the title
|
We are encountering the same issue. When the nameserver stateful set restarts, the nameserver controller reconciles every 6 seconds. During this process, if a partial nameserver is updated, the controller reconciles the partial nameserver's pod IP list. Subsequently, the broker controller updates the partial list to the broker and then updates the broker stateful set. As a result, the updated broker pod receives the partial nameserver pod IP list. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the issue:
There is inconsistent Broker data being retrieved when querying different RocketMQ NameServers. This inconsistency could potentially lead to issues with message routing and client connections within a distributed RocketMQ setup.
Expected Result:
The Broker data retrieved from all NameServers should be consistent and identical, ensuring stable functionality throughout the RocketMQ cluster.
The text was updated successfully, but these errors were encountered: