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

fix(drain): delay queuekey for redis cluster #3074

Merged
merged 2 commits into from
Feb 14, 2025

Conversation

harperKKK
Copy link
Contributor

Why

fix crossslot error when running queue.drain() in redis cluster

How

replace '' key with queue.toKey('') to include hash tag

Copy link
Contributor

@manast manast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code does not seem correct to me. "baseKey" is not the delayed key, so it does not make sense to use it for deleting delayed jobs.

@manast
Copy link
Contributor

manast commented Feb 12, 2025

Ok; I get the intent now. I think the the solution would be to pass a new ARGV with a boolean to express if the delayed jobs should also be deleted or not, and always pass the delayed key, that should work. It was an odd pattern to have a key that can sometimes be undefined anyway.

@harperKKK
Copy link
Contributor Author

i update the drain script using a new ARGV.

Copy link
Collaborator

@roggervalf roggervalf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@roggervalf roggervalf merged commit 05ea32b into taskforcesh:master Feb 14, 2025
11 checks passed
github-actions bot pushed a commit that referenced this pull request Feb 14, 2025
## [5.40.5](v5.40.4...v5.40.5) (2025-02-14)

### Bug Fixes

* **drain:** pass delayed key for redis cluster ([#3074](#3074)) ([05ea32b](05ea32b))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants