Skip to content

LettuceStreamCommands.xRevRange uses async dedicated connection #2078

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.

Sign up for GitHub

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

Jump to bottom
Closed
mp911de opened this issue Jun 9, 2021 · 0 comments
Closed

LettuceStreamCommands.xRevRange uses async dedicated connection #2078

mp911de opened this issue Jun 9, 2021 · 0 comments
Assignees
@mp911de
Labels
type: regression A regression from a previous release
Milestone
2.5.2 (2021.0.2)

Comments

@mp911de
Copy link
Member

mp911de commented Jun 9, 2021

We found out through occasional integration test failures, that XREVRANGE for Lettuce runs on a different connection which can lead to race conditions depending on the command timing. We should reuse the same connection.
@mp911de mp911de added the type: regression A regression from a previous release label Jun 9, 2021
@mp911de mp911de added this to the 2.5.2 (2021.0.2) milestone Jun 9, 2021
@mp911de mp911de self-assigned this Jun 9, 2021
mp911de added a commit that referenced this issue Jun 9, 2021
@mp911de
Fix XREVRANGE using Lettuce to use the same connection.
479b4a2 
XREVRANGE using Lettuce uses now the same connection instead of pinning execution to a dedicated connection.

Closes #2078
@mp911de mp911de closed this as completed in 866010e Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mp911de mp911de

Labels
type: regression A regression from a previous release
Projects
None yet
Milestone
2.5.2 (2021.0.2)
Development

No branches or pull requests
1 participant
@mp911de