You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
ubuntu
RocketMQ version
5.1.0
JDK Version
1.8.0
Describe the Bug
1、set enableScheduleAsyncDeliver=true
2、send some scheduled messages of each delay level.
3、pause master node for a while, the master will switch to slave. One way to pause is using remote debug.
4、after the master switch to slave, resume the slave, then CPU is high.
when master swith to slave, deliverExecutorService shuts down, this.future.thenAccept is not excuted, so the task is always RUNNING, causing endless loop in line 561 and line 569
Steps to Reproduce
1、set enableScheduleAsyncDeliver=true
2、send some scheduled messages of each delay level.
3、pause master node for a while, the master will switch to slave. One way to pause is using remote debug.
4、after the master switch to slave, resume the slave, then CPU is high.
What Did You Expect to See?
CPU is normal
What Did You See Instead?
CPU usage is high
Additional Context
No response
The text was updated successfully, but these errors were encountered:
…ue (#7262)
* [ISSUE #6390] Add break to the exception of WHEEL_TIMER_NOT_ENABLE.
* fix broker start fail if mapped file size is 0
* log
* only delete the last empty file
* change dataReadAheadEnable default to true
* fix endless loop when master change to slave.
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
RocketMQ version
5.1.0
JDK Version
1.8.0
Describe the Bug
1、set enableScheduleAsyncDeliver=true
2、send some scheduled messages of each delay level.
3、pause master node for a while, the master will switch to slave. One way to pause is using remote debug.
4、after the master switch to slave, resume the slave, then CPU is high.
the stack is in:
ScheduleMessageService.java: 561
when master swith to slave, deliverExecutorService shuts down, this.future.thenAccept is not excuted, so the task is always RUNNING, causing endless loop in line 561 and line 569
Steps to Reproduce
1、set enableScheduleAsyncDeliver=true
2、send some scheduled messages of each delay level.
3、pause master node for a while, the master will switch to slave. One way to pause is using remote debug.
4、after the master switch to slave, resume the slave, then CPU is high.
What Did You Expect to See?
CPU is normal
What Did You See Instead?
CPU usage is high
Additional Context
No response
The text was updated successfully, but these errors were encountered: