What is the difference between RocketMQ error system busy and broker busy

[smallemployees]

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

Linux node89 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

RocketMQ version

4.6.0

JDK Version

1.8

Describe the Bug

What is the difference between RocketMQ error system busy and broker busy

Steps to Reproduce

What is the difference between RocketMQ error system busy and broker busy

What Did You Expect to See?

What is the difference between RocketMQ error system busy and broker busy

What Did You See Instead?

What is the difference between RocketMQ error system busy and broker busy

Additional Context

No response

[qinyudong89]

Difference:

The reason why system busy and broker busy are thrown when messages are sent is that the PageCache is busy, which means that when a message is appended to the PageCache, the time taken for a single message to be sent is more than 1s, and if you continue to send messages to the Broker server and wait for them, the TPS cannot be satisfied at all. Therefore, the rapid failure mechanism will be used, directly to the message sender to return the error, the message sender will retry 2 times by default, the message will be sent to the other Broker, to ensure that it is highly available.

The solution is as follows:

1. Enable "read/write" separation
	Enable "read/write" separation by setting transientStorePoolEnable=true in broker.config. Disadvantage: Increase the possibility of data loss.
2. Expansion of the Broker server
	When the Broker server itself is busy, fast failure, and in the next period of time will avoid the Broker, so that the Broker recovery time guarantee, the Broker's own architecture is to support distributed horizontal expansion, increase the number of queues in the Topic, reduce the load on a single Broker server, so as to avoid the emergence of the PageCache. PageCache.

References

https://www.codingw.net/article?id=620

[github-actions]

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

[github-actions]

This issue was closed because it has been inactive for 3 days since being marked as stale.