Skip to content

There's no need for DefaultPullConsumer to rebalance. #8933

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

Closed
1 task done
humkum opened this issue Nov 15, 2024 · 0 comments · Fixed by #8934
Closed
1 task done

There's no need for DefaultPullConsumer to rebalance. #8933

humkum opened this issue Nov 15, 2024 · 0 comments · Fixed by #8934

Comments

@humkum
Copy link
Contributor

humkum commented Nov 15, 2024

Before Creating the Enhancement Request

  • I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

DefaultPullConsumer will specify the queue for consumption, and does not need rebalance to obtain queue allocation. We can add a switch to turn off the rebalance of DefaultPullConsumer to save client computing resources and also save unnecessary requests to the broker. #

Motivation

DefaultPullConsumer will specify the queue for consumption, and does not need rebalance to obtain queue allocation.

Describe the Solution You'd Like

Add a switch to turn off the rebalance of DefaultPullConsumer.

Describe Alternatives You've Considered

Stop the rebalance service
We can not stop the rebalance service directly because we may have not only one consumer object who using the same clientInstance.

Additional Context

No response

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.

1 participant