We have been using this library for quite some time without any issues, but we’ve now encountered the need to scale our Redis instance to cluster mode.
We have noticed that the beat process crashes with the following error.
redis.exceptions.ClusterCrossSlotError: Command # 3 (ZADD redbeat_staging-:schedule 1757272429 redbeat_staging-removing_users) of pipeline caused error: Keys in request don't hash to the same slot (context='within MULTI', command='zadd', original-slot='2686', wrong-slot='333', first-key='redbeat_staging-removing_users', violating-key='redbeat_staging-:schedule')
The Celery workers and the rest of our application are running without any issues.
We have been using this library for quite some time without any issues, but we’ve now encountered the need to scale our Redis instance to cluster mode.
We have noticed that the beat process crashes with the following error.
redis.exceptions.ClusterCrossSlotError: Command # 3 (ZADD redbeat_staging-:schedule 1757272429 redbeat_staging-removing_users) of pipeline caused error: Keys in request don't hash to the same slot (context='within MULTI', command='zadd', original-slot='2686', wrong-slot='333', first-key='redbeat_staging-removing_users', violating-key='redbeat_staging-:schedule')The Celery workers and the rest of our application are running without any issues.