Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broker's first registration may not take effect #4522

Closed
cserwen opened this issue Jun 28, 2022 · 0 comments · Fixed by #4523
Closed

Broker's first registration may not take effect #4522

cserwen opened this issue Jun 28, 2022 · 0 comments · Fixed by #4523

Comments

@cserwen
Copy link
Member

cserwen commented Jun 28, 2022

BUG REPORT

  1. Please describe the issue you observed:
  • What did you do (The steps to reproduce)?
    • restart namesrv .
    • 10s after namesrv starts, send a request to create a topic to one broker
  • What is expected to see?
    • namesrv should has routes of all topic
  • What did you see instead?
    • Only the routing information of the topic just created
  1. Please tell us about your environment:
  • OS: linux
  • branch: dev
  1. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
  • When the client sends a request to create a topic, the broker will register the routing information of the newly created topic to namesrv
  • But the broker may not have registered the all routing information to namesrv at the moment.
  • The following code will treat the request of the first step as the first registration, so that the first full registration of the broker will not take effect.
  • The broker will not be able to complete the full registration until the TopicConfigManager's dataversion is changed.
@duhenglucky duhenglucky added this to the 5.0.0 milestone Aug 10, 2022
duhenglucky pushed a commit that referenced this issue Aug 10, 2022
* fix topic route info not found in some case

* fix unit test about broker register

Co-authored-by: dengzhiwen1 <dengzhiwen1@xiaomi.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants