[GH-ISSUE #55] [BUG] In-progress tasks stick around in the face of redis failure #2038

New issue

Closed

opened 2026-03-15 18:52:05 +03:00 by kerem · 0 comments

kerem commented

2026-03-15 18:52:05 +03:00

Owner

Originally created by @hibiken on GitHub (Jan 17, 2020).
Original GitHub issue: https://github.com/hibiken/asynq/issues/55

Originally assigned to: @hibiken on GitHub.

Describe the bug
When using RedisFailoverClientOpt to take advantage of automatic failover, the tasks that are in-progress when the failover happens don't get removed from in-progress.

To Reproduce
Steps to reproduce the behavior (Code snippets if applicable):

Enqueue tasks (e.g. 100 tasks)
Start Background with RedisFailoverClientOpt
Disable redis master with redis-cli -p <port> DEBUG sleep 30 while some tasks are in progress.
After the failover, the Background will resume processing tasks, but the tasks that were in-progress never get removed from the asynq:in_progress list in redis.

Expected behavior
Upon successful failover, the tasks that were in-progress should be removed from the asynq:in_progress LIST

Environment (please complete the following information):

OS: MacOS
Version of asynq package: v0.1.0

Originally created by @hibiken on GitHub (Jan 17, 2020). Original GitHub issue: https://github.com/hibiken/asynq/issues/55 Originally assigned to: @hibiken on GitHub. **Describe the bug** When using `RedisFailoverClientOpt` to take advantage of automatic failover, the tasks that are in-progress when the failover happens don't get removed from in-progress. **To Reproduce** Steps to reproduce the behavior (Code snippets if applicable): 1. Enqueue tasks (e.g. 100 tasks) 2. Start `Background` with `RedisFailoverClientOpt` 3. Disable redis master with `redis-cli -p <port> DEBUG sleep 30` while some tasks are in progress. 4. After the failover, the `Background` will resume processing tasks, but the tasks that were in-progress never get removed from the `asynq:in_progress` list in redis. **Expected behavior** Upon successful failover, the tasks that were in-progress should be removed from the `asynq:in_progress` LIST **Environment (please complete the following information):** - OS: MacOS - Version of `asynq` package: v0.1.0

kerem

2026-03-15 18:52:05 +03:00

closed this issue
added the
bug
label

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#2038

No description provided.

Rows
Columns