Receiving extra connection/disconnection events on Redis server shutdown

Bug Report

Current Behavior

I’m trying to use the connection events to listen for when a connection has been made or lost and take appropriate actions. However, I often get extra connection/disconnection events that I don’t think should exist.

1. DisconnectedEvent [/127.0.0.1:55964 -> localhost/127.0.0.1:6379]
2. ConnectionDeactivatedEvent [/127.0.0.1:55964 -> localhost/127.0.0.1:6379]
Aug 07, 2018 4:20:42 PM io.lettuce.core.protocol.ConnectionWatchdog run
INFO: Reconnecting, last destination was localhost/127.0.0.1:6379
Aug 07, 2018 4:20:42 PM io.lettuce.core.protocol.ReconnectionHandler lambda$null$1
INFO: Reconnected to localhost:6379
3. ConnectedEvent [/127.0.0.1:55967 -> localhost/127.0.0.1:6379]
4. ConnectionActivatedEvent [/127.0.0.1:55967 -> localhost/127.0.0.1:6379]
5. DisconnectedEvent [/127.0.0.1:55967 -> localhost/127.0.0.1:6379]
6. ConnectionDeactivatedEvent [/127.0.0.1:55967 -> localhost/127.0.0.1:6379]

I am running Redis in Docker and just cycle through killing the container and restarting. The above logs are a for a single docker stop <container> command. You can see I get an additional event of each type after the initial disconnect events. This doesn’t happen every time I kill the container, but it happens very frequently.

Input Code

RedisClient redisClient = RedisClient.create("redis://localhost:6379");
redisClient.getResources().eventBus().get().subscribe(System.out::println);
redisClient.connect();

Expected behavior/code

I should only receive a disconnect event when the Redis server is shutdown instead of additional connection events.

Environment

• Lettuce version(s): 5.0.5.RELEASE
• Redis version: 4.0.10

[yissachar]

Got it, async is working fine for me.

Still confused as to the multiple events though. Is this expected or not?

[mp911de]

Yes, multiple events are expected. See Connection-Events.