qinyudong89 commented on issue #8451:
URL: https://github.com/apache/rocketmq/issues/8451#issuecomment-2254563011
### 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
