[GH-ISSUE #650] How to ensure that the tasks in redis will not be lost after the service stops for a long time #322

Closed
opened 2026-03-02 05:20:28 +03:00 by kerem · 4 comments
Owner

Originally created by @fms5cmS on GitHub (Apr 30, 2023).
Original GitHub issue: https://github.com/hibiken/asynq/issues/650

When i stop my server a long time, the tasks in redis lost, and tell me "[queue](asynq: queue not found)".

Do i need some config for this ?

Originally created by @fms5cmS on GitHub (Apr 30, 2023). Original GitHub issue: https://github.com/hibiken/asynq/issues/650 When i stop my server a long time, the tasks in redis lost, and tell me "[queue](asynq: queue not found)". Do i need some config for this ?
kerem closed this issue 2026-03-02 05:20:28 +03:00
Author
Owner

@kamikazechaser commented on GitHub (May 3, 2023):

Are you persisting your redis data between restarts?

<!-- gh-comment-id:1532532133 --> @kamikazechaser commented on GitHub (May 3, 2023): Are you persisting your redis data between restarts?
Author
Owner

@fms5cmS commented on GitHub (May 8, 2023):

I just restarted my server by kill -15 server not Redis, so I do not need to persist Redis data.

Is the problem that I put the asynq server and client in the same application which I restarted?

<!-- gh-comment-id:1537647816 --> @fms5cmS commented on GitHub (May 8, 2023): I just restarted my server by `kill -15 server` not Redis, so I do not need to persist Redis data. Is the problem that I put the asynq server and client in the same application which I restarted?
Author
Owner

@kamikazechaser commented on GitHub (May 8, 2023):

You need to persist redis data if you want don't want to lose tasks. Start your redis server with redis-server --save 60 1 --loglevel warning.

<!-- gh-comment-id:1537852671 --> @kamikazechaser commented on GitHub (May 8, 2023): You need to persist redis data if you want don't want to lose tasks. Start your redis server with `redis-server --save 60 1 --loglevel warning`.
Author
Owner

@ioannidesalex commented on GitHub (Jul 8, 2023):

That's not really an issue with asynq.

<!-- gh-comment-id:1627532457 --> @ioannidesalex commented on GitHub (Jul 8, 2023): That's not really an issue with asynq.
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#322
No description provided.