-
Notifications
You must be signed in to change notification settings - Fork 0
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
[SPIKE] Persisted Job Queue or Retry Logic #49
Comments
frrist
added a commit
that referenced
this issue
Mar 15, 2025
- closes #49 - thank you OS contributor: https://github.com/maragudk/goqite/ - Licence and credit at top of respective files - modified from source to allow generics
frrist
added a commit
that referenced
this issue
Mar 15, 2025
- closes #49 - thank you OS contributor: https://github.com/maragudk/goqite/ - Licence and credit at top of respective files - modified from source to allow generics
@hannahhoward needs to review |
frrist
added a commit
that referenced
this issue
Mar 18, 2025
- closes #49 - thank you OS contributor: https://github.com/maragudk/goqite/ - Licence and credit at top of respective files - modified from source to allow generics
frrist
added a commit
that referenced
this issue
Apr 9, 2025
- closes #49 - thank you OS contributor: https://github.com/maragudk/goqite/ - Licence and credit at top of respective files - modified from source to allow generics
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement:
When aggregating pieces or submitting aggregations, failures may occur due to software-related issues or unexpected storage node restarts.
Expected Behavior:
Jobs in the "job queue" must be retried until they succeed. If a job fails, it should either:
At present when jobs fail, or the node restarts the contents of the queue is lost.
Ideas
One approach may be to implement or adopt a job queuing library with persistence. (e.g. https://github.com/maragudk/goqite)
Another option could be to persist jobs to a store (we already have one) in a pending state, and ensure they are completed across restarts and failures.
The text was updated successfully, but these errors were encountered: