What Should Be Noted When Using Redis for Pub/Sub?

Updated on 2022-09-15 GMT+08:00

View PDF

The Redis official website describes Pub/Sub in detail. When using Redis for Pub/Sub, note the following:

Your client must process messages in a timely manner.
Your client subscribes to a channel. If it does not receive messages in a timely manner, DCS instance messages may be overstocked. If the size of accumulated messages reaches the threshold (32 MB by default) or remains at a certain level (8 MB by default) for a certain period of time (1 minute by default), your client will be automatically disconnected to prevent server memory exhaustion.
Your client must support connection re-establishment in case of disconnection.
In the event of a disconnection, you need to run the subscribe or psubscribe command on your client to subscribe to a channel again. Otherwise, your client cannot receive messages.
Do not use pub/sub in scenarios with high message reliability requirements.
The Redis pub/sub is not a reliable messaging system. Messages that are not retrieved will be discarded when your client is disconnected or a master/standby switchover occurs.

Parent topic: Client and Network Connection

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel