[GH-ISSUE #854] UNKNOWN: redis command error: SADD failed: READONLY You can't write against a read only replica. #420

Open
opened 2026-03-02 05:21:05 +03:00 by kerem · 2 comments
Owner

Originally created by @avvari-da on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/854

Originally assigned to: @hibiken on GitHub.

Describe the bug
Getting the following error randomly.
UNKNOWN: redis command error: SADD failed: READONLY You can't write against a read only replica.
Finding a tough time figuring out the issue.

Additional context
Am using Redis Sentinel on Kubernetes.

Please help!
Thanks in advance.

Originally created by @avvari-da on GitHub (Apr 6, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/854 Originally assigned to: @hibiken on GitHub. **Describe the bug** Getting the following error randomly. `UNKNOWN: redis command error: SADD failed: READONLY You can't write against a read only replica.` Finding a tough time figuring out the issue. **Additional context** Am using Redis Sentinel on Kubernetes. Please help! Thanks in advance.
Author
Owner

@cold-bin commented on GitHub (May 4, 2024):

can your redis perform config set readonly no in redis-cli after data migrated?

<!-- gh-comment-id:2094109977 --> @cold-bin commented on GitHub (May 4, 2024): can your redis perform `config set readonly no` in redis-cli after data migrated?
Author
Owner

@hernandikrammes commented on GitHub (May 23, 2024):

We identify that on this situation the use of CPU on kubernetes get very high. Someone could validate that too?

<!-- gh-comment-id:2127733386 --> @hernandikrammes commented on GitHub (May 23, 2024): We identify that on this situation the use of CPU on kubernetes get very high. Someone could validate that too?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#420
No description provided.