-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Job service will report cross slot error when work with redis cluster #4633
Comments
The redis cluster is 3 master+ 3 slave case. this can be reproduce with only two master node. |
This issue is from the dependent library and we may need time to let the maintainers or submit PR to fix it. Probably, it would become a limitation of v 1.5.0. |
No time to complete it at SP34, move to SP35 |
Try the version 0.5.1 of package github.com/gocraft/work, the issue still there. Move this out of target 1.6.0. |
set to priority HA as it blocks HA. |
This commit upgrdes the github.com/gocraft/work package to 0.5.1 and updates the namespace value to fix the redis cross slot issue mentioned in goharbor#4633
This commit upgrdes the github.com/gocraft/work package to 0.5.1 and updates the namespace value to fix the redis cross slot issue mentioned in goharbor#4633
This commit upgrdes the github.com/gocraft/work package to 0.5.1 and updates the namespace value to fix the redis cross slot issue mentioned in goharbor#4633
Done |
Apr 11 22:53:03 172.18.0.1 jobservice[971]: message repeated 439 times: [ ERROR: worker.fetch - CROSSSLOT Keys in request don't hash to the same slot]
Apr 11 22:53:03 172.18.0.1 jobservice[971]: ERROR: requeuer.process - CROSSSLOT Keys in request don't hash to the same slot
Apr 11 22:53:03 172.18.0.1 jobservice[971]: ERROR: requeuer.process - CROSSSLOT Keys in request don't hash to the same slot
Apr 11 22:53:03 172.18.0.1 jobservice[971]: ERROR: worker.fetch - CROSSSLOT Keys in request don't hash to the same slot
https://stackoverflow.com/questions/38042629/redis-cross-slot-error
The text was updated successfully, but these errors were encountered: