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

[Native] concurrency rebalance will lead to inconsistency, which will cause no message consuimg #313

Closed
xujianhai666 opened this issue Nov 27, 2019 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@xujianhai666
Copy link
Member

The issue tracker is ONLY used for the go client (feature request of RocketMQ need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.

Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.

Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as to the following:

BUG REPORT
Please add the branch name [Native]/[Master] at the header of the Isssue title.

  1. Please describe the issue you observed:

    • What did you do (The steps to reproduce)?
      rebalance is concurrent, which will cause processQueue status and processQueueTable contennt inconsistency, which lead to no message read on production.

    • What did you expect to see?

    • What did you see instead?

  2. Please tell us about your environment:

    • What is your OS?

    • What is your client version?

    • What is your RocketMQ version?

  3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

FEATURE REQUEST

  1. Please describe the feature you are requesting.

  2. Provide any additional detail on your proposed use case for this feature.

  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

@wenfengwang wenfengwang added this to the 2.0.0-RC1 milestone Nov 28, 2019
@wenfengwang wenfengwang added the bug Something isn't working label Nov 28, 2019
xujianhai666 added a commit to xujianhai666/rocketmq-client-go that referenced this issue Dec 1, 2019
- add rbMutex for client rebalance
- use atomic value to avoid concurrency

Closes apache#313
xujianhai666 added a commit to xujianhai666/rocketmq-client-go that referenced this issue Dec 1, 2019
- add rbMutex for client rebalance
- use atomic value to avoid concurrency

Closes apache#313
wenfengwang pushed a commit that referenced this issue Dec 10, 2019
- add rbMutex for client rebalance
- use atomic value to avoid concurrency

Closes #313
@wenfengwang
Copy link
Member

wenfengwang commented Dec 10, 2019

close due to #316

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants