Recommended to use separate queues for QoS 2 publish messages and reliability (rel) messages

[xinyi-xs]

Massive qos 2 message in high rate will be bloked, emqx trace log give me hints that too many qos 2 publish message without rel response will cause error

2023-06-03T08:44:30+00:00 [SOCKET] [email protected]:50498 msg: socket_force_closed, reason: receive_maximum_exceeded
2023-06-03T08:44:30+00:00 [SOCKET] [email protected]:50498 msg: emqx_connection_terminated, reason: {shutdown,receive_maximum_exceeded}

It is generally recommended to use separate queues for QoS 2 publish messages and reliability (rel) messages. This is because QoS 2 publish messages require a higher level of assurance that they are delivered to the broker and subscribers, while reliability messages may have different requirements and characteristics.

Separating the queues allows for more granular control over the message delivery process, which can help ensure that QoS 2 messages are prioritized and handled in a timely manner. It can also help prevent reliability messages from clogging up the queue and potentially delaying the delivery of more important messages.

In addition, using separate queues can make it easier to monitor and troubleshoot message delivery issues, as each queue can be independently monitored and analyzed.

Overall, while it is possible to use a single queue for both QoS 2 publish messages and reliability messages, using separate queues is generally considered to be a best practice for optimizing message delivery and ensuring reliable communication.