-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Retry into Queue Lib #17
Conversation
Git ignored when I renamed it from e2e to E2E so I had to manually mv it using the cli
How is the retry strategy applied in production? As far as I can see here right now, is that we manually need to retry and it just works of all failed jobs. I am not sure if this is the most sane approach. Usually with all common libraries, the retry configuration is tied to a job. Meaning you enqueue a job while defining how its going to be retried. I am not sure if blindly just working of failed jobs is good. We dont know how many times a job has been retried, etc. ref: |
Right, I'll try and so some research and think of something better |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is the sum method I saw in the Appwrite PR? I can't seem to find it.
This PR implements Retry functionality into the Queue library, it will take all failed jobs in
{namespace}.failed.{queue}
and re-queue them while removing them from that list.