hzh0425 opened a new issue, #5799: URL: https://github.com/apache/rocketmq/issues/5799
Apache RocketMQ, like all messaging systems, imposes a size limit on each message sent to a broker. This prevents the load per message from exceeding the maxMessageSize set in the broker, which defaults to 4 MB. However, in application scenarios such as image processing and audio processing, many users need RocketMQ clients to send large messages to brokers. You can achieve this by adjusting maxMessageSize. However, this approach can cause many problems. For example, if a client publishes a 100 MB message, and the broker allows storing the message to disk, the broker will spend a lot of IO resources processing the message. This will affect broker flushing performance and cause a backlog of messages. Therefore, when RocketMQ sends large messages, in addition to increasing the value of maxMessageSize, we can also support the 'message chunking' function. Through message chunking, producers can split large messages into multiple chunks according to maxMessageSize, and send each chunk to the broker as a normal message. The consumer will then assemble these chunked messages back into the original message. *Therefore, it's time to discuss whether 'message chunking' should be supported or not.* -- 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]
