Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NOAUTH after full queue and reconnect #691

Closed
mp911de opened this issue Feb 7, 2018 · 2 comments
Closed

NOAUTH after full queue and reconnect #691

mp911de opened this issue Feb 7, 2018 · 2 comments
Labels
type: bug A general bug
Milestone

Comments

@mp911de
Copy link
Collaborator

mp911de commented Feb 7, 2018

com.lambdaworks.redis.protocol.ConnectionWatchdog[] INFO Reconnecting, last destination was 
com.lambdaworks.redis.protocol.CommandHandler[] WARNING [chid=0x17, channel=0xa1ed60d5, ######## -> ] Unexpected exception during request: com.lambdaworks.redis.RedisException: Request queue size exceeded: 100. Commands are not accepted until the queue size drops.
com.lambdaworks.redis.RedisException: Request queue size exceeded: 100. Commands are not accepted until the queue size drops.
@mp911de mp911de added the type: bug A general bug label Feb 7, 2018
@mp911de mp911de added this to the Lettuce 4.4.3 milestone Feb 7, 2018
@mp911de
Copy link
Collaborator Author

mp911de commented Feb 16, 2018

Happens if using Lettuce 4.3 (Ping before connect/calling auth(…)/passing RedisURI with password). Ping before connect auth is fixed in Lettuce 4.4. Calling auth(…) is still broken.

@mp911de
Copy link
Collaborator Author

mp911de commented Feb 16, 2018

Increasing the number of allowed commands by the maintenance command limit seems to be a good fit for an intermediate fix. More of a patch, see also #697.

mp911de added a commit that referenced this issue Feb 16, 2018
…#691

Request queue size checks now consider an additional number of connection activation commands.
mp911de added a commit that referenced this issue Feb 16, 2018
…#691

Request queue size checks now consider an additional number of connection activation commands.
mp911de added a commit that referenced this issue Feb 16, 2018
…#691

Request queue size checks now consider an additional number of connection activation commands.
mp911de added a commit that referenced this issue Feb 16, 2018
…#691

Request queue size checks now consider an additional number of connection activation commands.
@mp911de mp911de closed this as completed Feb 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant