-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Cocytus wrote:
If the remote EC2 node goes dark for a bit (ie: reboot), the local stunnel client will reconnect, however the internal process which is establishing its connection to the local stunnel client does not get disconnected and therefore doesn't know that redis became unavailable and needs to re-subscribe to the redis stream. I need to invalidate the established session when the remote reconnects.
Do you see anything in your log files indicating that stunnel gets notified about the peer being disconnected? If not then stunnel does not make any difference for you. You would bump into the same issue without stunnel.
Either way, you need some kind of keepalive. It may be implemented either at the application level by periodically sending a command (some no-op) to your redis server, or at the TCP level. Stunnel can help you with it. The stunnel.conf option is: socket = r:SO_KEEPALIVE=1
Mike