We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
Ubuntu 24.04
5.3.1
1.8
Bad performace of delay message in rocksdb consumequeue
storeType=defaultRocksDB
cd benchmark;sh producer.sh -n localhost:9876 -t testTopic -d true -e 2
mqadmin topicstatus -n localhost:9876 -t SCHEDULE_TOPIC_XXXX
cat ${storeRootPath}/config/delayOffset.json
delay message are deliverd quick.
delay message are deliverd slow.
No response
The text was updated successfully, but these errors were encountered:
[ISSUE apache#8765] fix low performance of delay message when enable …
c7597fb
…rocksdb consume queue
Successfully merging a pull request may close this issue.
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
Ubuntu 24.04
RocketMQ version
5.3.1
JDK Version
1.8
Describe the Bug
Bad performace of delay message in rocksdb consumequeue
Steps to Reproduce
storeType=defaultRocksDB
in broker.confcd benchmark;sh producer.sh -n localhost:9876 -t testTopic -d true -e 2
mqadmin topicstatus -n localhost:9876 -t SCHEDULE_TOPIC_XXXX
cat ${storeRootPath}/config/delayOffset.json
What Did You Expect to See?
delay message are deliverd quick.
What Did You See Instead?
delay message are deliverd slow.
Additional Context
No response
The text was updated successfully, but these errors were encountered: