How to handle connection interruption/timeout in PubSub listen() ?

What happens when connection to Redis goes down or timeouts while listening to PubSub messages via a long running “pubsub.listen()” ? Any tips how i can gracefully handle / restart interrupted connection? I do appreciate your help!

This is the relevant code:

class Listener(threading.Thread):
    def __init__(self, r, channels):
        threading.Thread.__init__(self)
        self.redis = r
        self.pubsub = self.redis.pubsub()
        try:
            self.pubsub.subscribe(channels)
        except ConnectionError:
            print self, "Redis is down"

    def work(self, item):
        print item['channel'], ":", item['data']

    def run(self):
        for item in self.pubsub.listen():
            if item['data'] == "KILL":
                self.pubsub.unsubscribe()
                print self, "unsubscribed and finished"
                break
            else:
                self.work(item)

[pmdscully]

Hi @andymccurdy and all, I realise the issue is closed, but I still experienced the issue. I would like to recommend a readme update to include explicit shutdown order for removal of the thread interruption error with pubsub, mentioned. For me, this has removed exceptions errors caused by interruption of the thread created in run_in_thread() during application shutdown.

This for the use case as follows:

    p = r.pubsub()
    p.subscribe( **{key: handler_func} )
    t = p.run_in_thread(sleep_time=0.1)

then explicit order for shutdown is:

    t.stop()
    t.join()
    p.close()

Optionally wrapped in try/excepts.

I’m using PyPi release v3.3.8.

Hopefully that will help someone in future with the same issue. Thanks,

[sriman]

I have faced this problem mainly because I am using elastic cache of aws it tends to close the connection sometimes, no specific usecase when it happens, in the python code whenever connection closes its not reconnected again. thats why subscriber can’t listen to the signal to the subscribe, to solve this there is option called socket keep alive in this library, give a shot with that option

On Sat 28 Apr, 2018, 12:48 PM yuzhushang, [e-mail] wrote:

hi @sriman https://github.com/sriman

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/andymccurdy/redis-py/issues/386#issuecomment-385148175, or mute the thread https://github.com/notifications/unsubscribe-auth/ACLmXS54h7W6Z4zRnEnJE30xwfkV3as2ks5ttBevgaJpZM4BEVVc .