Lettuce RedisClusterClient calls AUTH twice #313

Closed
mp911de opened this Issue Jul 20, 2016 · 0 comments

Projects

None yet

1 participant

@mp911de
Owner
mp911de commented Jul 20, 2016

On startup with a password-protected cluster, the client calls AUTH twice
log:

2016-07-20 13:27:09.062 DEBUG 12352 --- [           main] c.l.redis.cluster.RedisClusterClient     : connectNode(hostname/111.222.333.444:6380)
2016-07-20 13:27:09.119 DEBUG 12352 --- [           main] c.l.r.r.DefaultEventLoopGroupProvider    : Adding reference to io.netty.channel.nio.NioEventLoopGroup@7c2924d7, existing ref count 0
2016-07-20 13:27:09.122 DEBUG 12352 --- [           main] com.lambdaworks.redis.RedisClient        : Connecting to Redis at hostname/111.222.333.444:6380
2016-07-20 13:27:09.576 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.ConnectionWatchdog    : null channelActive(io.netty.channel.DefaultChannelHandlerContext@44f1e779)
2016-07-20 13:27:09.576 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] channelActive()
2016-07-20 13:27:09.576 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] moveQueuedCommandsToCommandBuffer 0 command(s) added to buffer
2016-07-20 13:27:09.576 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] activateCommandHandlerAndExecuteBufferedCommands 0 command(s) buffered
2016-07-20 13:27:09.577 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] activating channel handler
2016-07-20 13:27:09.577 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Commands []
2016-07-20 13:27:09.578 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] channelActive() done
2016-07-20 13:27:09.578 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.ConnectionWatchdog    : null userEventTriggered(io.netty.channel.DefaultChannelHandlerContext@44f1e779, SslHandshakeCompletionEvent(SUCCESS))
2016-07-20 13:27:09.579 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.ConnectionWatchdog    : null userEventTriggered(io.netty.channel.DefaultChannelHandlerContext@44f1e779, com.lambdaworks.redis.ConnectionEvents$Activated@7618cb13)
2016-07-20 13:27:09.581 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Command Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.581 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Command Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.582 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() done
2016-07-20 13:27:09.583 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandEncoder        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] writing command Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.584 TRACE 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandEncoder        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Sent: *2
$4
AUTH
$44
XXXXXXXXXX
2016-07-20 13:27:09.609 TRACE 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Received: +OK
2016-07-20 13:27:09.610 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Queue contains: 1 commands
2016-07-20 13:27:09.610 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.RedisStateMachine     : Decode Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.611 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.RedisStateMachine     : Decoded Command [type=AUTH, output=StatusOutput [output=OK, error='null']], empty stack: true
2016-07-20 13:27:09.616 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Command Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.616 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Command Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.617 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() done
2016-07-20 13:27:09.617 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandEncoder        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] writing command Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.618 TRACE 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandEncoder        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Sent: *2
$4
AUTH
$44
XXXXXXXXXX
2016-07-20 13:27:09.642 TRACE 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Received: +OK
2016-07-20 13:27:09.642 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Queue contains: 1 commands
2016-07-20 13:27:09.642 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.RedisStateMachine     : Decode Command [type=AUTH, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.643 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.RedisStateMachine     : Decoded Command [type=AUTH, output=StatusOutput [output=OK, error='null']], empty stack: true
2016-07-20 13:27:09.644 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.645 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() writeAndFlush Command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.645 DEBUG 12352 --- [           main] c.l.redis.protocol.CommandHandler        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] write() done
2016-07-20 13:27:09.645 DEBUG 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandEncoder        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] writing command TimedAsyncCommand [type=CLUSTER, output=StatusOutput [output=null, error='null']]
2016-07-20 13:27:09.645 TRACE 12352 --- [ioEventLoop-3-1] c.l.redis.protocol.CommandEncoder        : [/192.168.55.59:62874 -> hostname/111.222.333.444:6380] Sent: *2
$7
CLUSTER
$5
NODES
@mp911de mp911de added this to the Lettuce 4.2.2 milestone Jul 20, 2016
@mp911de mp911de added a commit that referenced this issue Jul 20, 2016
@mp911de Don't call AUTH in topology refresh #313
RedisClusterClient performs already authentication in the connectAsyncImpl method so there's no need to authenticate again.
fdce018
@mp911de mp911de added a commit that referenced this issue Jul 20, 2016
@mp911de Don't call AUTH in topology refresh #313
RedisClusterClient performs already authentication in the connectAsyncImpl method so there's no need to authenticate again.
20ada0b
@mp911de mp911de added a commit that referenced this issue Jul 20, 2016
@mp911de Don't call AUTH in topology refresh #313
RedisClusterClient performs already authentication in the connectAsyncImpl method so there's no need to authenticate again
71c6177
@mp911de mp911de added a commit that referenced this issue Jul 20, 2016
@mp911de Don't call AUTH in topology refresh #313
RedisClusterClient performs already authentication in the connectAsyncImpl method so there's no need to authenticate again
203b7cd
@mp911de mp911de closed this Jul 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment