-
Notifications
You must be signed in to change notification settings - Fork 452
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
Enhance the queue failed jobs functionality. #8306
Comments
I like it but I suggest a much longer window before removing failed jobs. Maybe 6 months? I think that in some cases failed jobs will be one way that people audit when things have gone wrong, and they may not recognize a problem for a while. This may be especially true with metadata deposits (eg - Crossref) where someone might not realize that their work has failed to be deposited for a long time. |
How about we set it as a config option in number of days ? and if thats turned off or disabled , the schedule task will not run. better control than hard coded values . |
Yes, that sounds good. |
@asmecher Please take a look at this. |
Looks very promising so far, @touhidurabir! I like the simplification you've proposed as well. I've left a few comments. |
* pkp/pkp-lib#8306 Failed jobs UI * pkp/pkp-lib#8306 Added failed job details page * pkp/pkp-lib#8306 Moved job data fetch to API * pkp/pkp-lib#8306 UI enhancement * pkp/pkp-lib#8306 code cleanup by extending JobsPage in FailedJobsPage component
All merged -- thanks, @touhidurabir and @NateWr! |
#8306 Patch for zero-length delimited identifier issue
pkp/pkp-lib#8306 Submodule Update ##touhidurabir/i8306_patch_main##
pkp/pkp-lib#8306 Submodule Update ##touhidurabir/i8306_patch_main##
pkp/pkp-lib#8306 Submodule Update ##touhidurabir/i8306_patch_main##
Builds are failing for Patch PRs Changes are pushed and merged also tested in local |
All tests are passing now . |
Describe the enhancement
We have a frontend UI implemented to view queue pending/waiting to execute queue jobs in #7171 also queue job execution/handling enhancement in #7105 . But have no UI or CLI functionality to view or manage failed jobs and associated error for those failed job. It can be a good enhancement to have following functionalities for better managing of failed jobs
Who is asking for this one?
No one right now. But this will give both the devs and site admins each access to failed jobs with better visualisation.
Possible UI Update(screenshots)



Previous Idea
Clear out much older failed jobs from the
failed_jobs
table. Suggestion is to run a schedule task once a week and clear out any failed jobs older that 2 weeks from the table to keep it cleaner . This can also include some enhancement to existing job cli tool for better failed jobs handling.PRs
ojs --> pkp/ojs#3763
omp --> pkp/omp#1298
ops --> pkp/ops#472
pkp-lib --> #8534
ui-library --> pkp/ui-library#248
The text was updated successfully, but these errors were encountered: