In general, Glide handles all error scenarios, and no extra logic from the application is required.

The best practice is to have a dedicated client for pub/sub since Glide initiates disconnections to ensure that all unsubscriptions succeed during topology updates.

Glide detects topology updates and with server errors, such as MOVED or connection error. Additionally, it periodically checks the health of the connections and auto-reconnects. It also periodically checks for topology updates by calling 'CLUSTER SLOTS'.

You can also review the docs at https://github.com/valkey-io/valkey-glide/wiki/General-Concepts#pubsub-support