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

[Bug] consumerManagerThreadPoolQueueCapacity has settings but is not used #8057

Open
3 tasks done
frinda opened this issue Apr 24, 2024 · 2 comments
Open
3 tasks done

Comments

@frinda
Copy link
Contributor

frinda commented Apr 24, 2024

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

SUSE Linux Enterprise Server 12 SP5

RocketMQ version

4.9.x

JDK Version

JDK 8

Describe the Bug

consumerManagerThreadPoolQueueCapacity has settings but is not used
https://github.com/apache/rocketmq/blob/4.9.x/broker/src/main/java/org/apache/rocketmq/broker/BrokerController.java

Steps to Reproduce

NA

What Did You Expect to See?

consumerManagerThreadPoolQueueCapacity has settings and be used

What Did You See Instead?

consumerManagerThreadPoolQueueCapacity has settings but is not used

Additional Context

No response

@humkum
Copy link
Contributor

humkum commented Apr 24, 2024

The consumerManageExecutor is initialized as a newFixedThreadPool, which's queue size is Integer.MAX_VALUE. What's the value do you want to set? And did you meet some problems caused by this parameter?

@frinda
Copy link
Contributor Author

frinda commented Apr 26, 2024

I haven't had a problem because of this. but this may cause OOM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants