[GH-ISSUE #212] Hang up for a long time and enter failed in about half an hour #747

Closed
opened 2026-03-15 21:26:50 +03:00 by kerem · 4 comments
Owner

Originally created by @tinnkai on GitHub (Feb 4, 2022).
Original GitHub issue: https://github.com/hibiken/asynqmon/issues/212

How to solve this situation? Thank you.
1643990450(1)

Originally created by @tinnkai on GitHub (Feb 4, 2022). Original GitHub issue: https://github.com/hibiken/asynqmon/issues/212 How to solve this situation? Thank you. ![1643990450(1)](https://user-images.githubusercontent.com/2200272/152561183-c28cac0d-c984-47fa-925b-d377c30a0d05.jpg)
kerem closed this issue 2026-03-15 21:26:56 +03:00
Author
Owner

@hibiken commented on GitHub (Feb 4, 2022):

@tinnkai thank you for opening an issue!

Would you mind showing the output of

redis-cli ZRANGE asynq:{default}:deadlines 0 -1 WITHSCORES
<!-- gh-comment-id:1030197142 --> @hibiken commented on GitHub (Feb 4, 2022): @tinnkai thank you for opening an issue! Would you mind showing the output of ```sh redis-cli ZRANGE asynq:{default}:deadlines 0 -1 WITHSCORES ```
Author
Owner

@tinnkai commented on GitHub (Feb 5, 2022):

@hibiken
image
It may be caused by the direct shutdown of the service while the queue is being processed,But what I expect can I keep the failure queue and then I can do it manually.
thank you

<!-- gh-comment-id:1030581406 --> @tinnkai commented on GitHub (Feb 5, 2022): @hibiken ![image](https://user-images.githubusercontent.com/2200272/152634928-e5f39a14-10f8-44c9-999c-b3ee9734ce00.png) It may be caused by the direct shutdown of the service while the queue is being processed,But what I expect can I keep the failure queue and then I can do it manually. thank you
Author
Owner

@tinnkai commented on GitHub (Feb 5, 2022):

@hibiken
Sorry, I misunderstood. Processed includes the number of failed and successful, that is, entering failed will retry
image

<!-- gh-comment-id:1030617538 --> @tinnkai commented on GitHub (Feb 5, 2022): @hibiken Sorry, I misunderstood. Processed includes the number of failed and successful, that is, entering failed will retry ![image](https://user-images.githubusercontent.com/2200272/152642676-5c418ba6-9766-43cb-a58b-6d0b5698ee28.png)
Author
Owner

@hibiken commented on GitHub (Feb 5, 2022):

@tinnkai Thanks for providing additional info!

I think initial confusion around task being stuck in "active" state is due to how the task recovery works currently when a worker crashes (or forced killed kill -9). Currently, asynq recovers task if its deadline has expired over 30s ago, but we have an open issue to improve this by recovering these orphaned tasks more quickly (https://github.com/hibiken/asynq/issues/334).

<!-- gh-comment-id:1030669245 --> @hibiken commented on GitHub (Feb 5, 2022): @tinnkai Thanks for providing additional info! I think initial confusion around task being stuck in "active" state is due to how the task recovery works currently when a worker crashes (or forced killed `kill -9`). Currently, asynq recovers task if its deadline has expired over 30s ago, but we have an open issue to improve this by recovering these orphaned tasks more quickly (https://github.com/hibiken/asynq/issues/334).
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/asynqmon#747
No description provided.