When the master node of RocketMQ 5.1.4 version crashes, scheduled messages cannot be delivered normally

[sqtce]

Before Creating the Bug Report

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

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

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

Runtime platform environment

Linux

RocketMQ version

5.1.4

JDK Version

1.8.0

Describe the Bug

After the primary Broker node crashes, scheduled messages that were not delivered in time cannot be consumed normally, leading to the loss of these messages. However, once the Broker primary node is restarted, the system will return to normal, and messages can be consumed normally

Steps to Reproduce

After the primary Broker node goes down

What Did You Expect to See?

What are the solutions

What Did You See Instead?

None

Additional Context

No response

[RongtongJin]

If there is no switch, the master broker will be offline, and the slave broker will not be able to deliver schedule messages normally.

[sqtce]

My deployment architecture is master-slave mode. After the master node goes down, what solutions are available in master-slave mode to enable the slave to continue sending scheduled messages normally?

[gaoyf]

My deployment architecture is master-slave mode. After the master node goes down, what solutions are available in master-slave mode to enable the slave to continue sending scheduled messages normally?

FYI：https://github.com/apache/rocketmq/blob/develop/docs/cn/SlaveActingMasterMode.md