I would like to know if there is a way to rescue redis connection errors, so that I can use a alternative datastore to push jobs. We use client side middleware to set current thread user etc, so rescuing .perform_async wouldn't be of much help. Also, Client side middleware doesn't seem to support error handling. Is there a workaround somehow that I can rescue for redis connection errors inside client middleware? The approach that I could think of was implement a heartbeat to redis, set a global flag to push jobs to an alternative datastore inside middleware. Any help is appreciated.Thanks.
--
You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/78d43738-64e0-4b4c-bce1-65c266fe294b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/630e4642-493a-483a-9b95-c5138cc0510e%40googlegroups.com.