If connection to db lost then deno process die and pup/sub not resuming. about redis HOT 7 CLOSED

As a first step, I created a test to reproduce the issue that @devalexqt reported. If it makes sense, I can look into suggesting a fix. #92

from redis.

@Terkwood that was my idea. I’ve been working on a solution for the past few days; finishing testing. I hope I can push tomorrow for you all to see.

from redis.

Problem

I think the problem is that once connection is lost, the subscriber never resumes.

Solutions

To resolve the above problem, I think that deno-redis should do the following things:

• provides a way to reconnect the lost connection.
• resumes (all?) subscribers when reconnected.

What about the other libraries?

ioredis provides the auto-reconnect and auto-resubscribe features:

new Redis({
  maxRetriesPerRequest: 5,
  autoResubscribe: true, // When reconnected, the subscriber will also resume.
  retryStrategy: times => computeNextTimeout(times),
});

go-redis

PubSub automatically reconnects to Redis Server and resubscribes to the channels in case of network errors.

https://pkg.go.dev/github.com/go-redis/[email protected]+incompatible?tab=doc#PubSub

from redis.

@devalexqt @Terkwood @sebastienfilion I'm sorry for the delay response.
I've organized my thoughts.
If you have any other ideas, please leave comments! 😄

from redis.

I vote to resume all subscribers when reconnected.

If others like the idea of auto-reconnect, that sounds good to me, too.

from redis.

Nicely documented! I think the next step here is for another person to reproduce this(probably not so hard), and make a suggestion on how to improve it.

from redis.

Any news?

from redis.