This repository was archived by the owner on Jan 15, 2022. It is now read-only.
COMMONS-586 (#429) #616
Merged
COMMONS-586 (#429) #616
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After 5.2.4->5.3.0 migration daily and weekly jobs are restarted at same time due to long time without execution. The 2 jobs try to clean notifs and notif params without digest. As we are clean digest in ResumeDigestJobupgradePlugin, there are a lot of row to delete, and job are in conflict and generate a transaction exception This change add the notification clean up before resume the jobs, and after deleting digest if necessary. So When Job are executed, they read tables, find no rows, and exited, without error.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After 5.2.4->5.3.0 migration daily and weekly jobs are restarted at same time due to long time without execution.
The 2 jobs try to clean notifs and notif params without digest.
As we are clean digest in ResumeDigestJobupgradePlugin, there are a lot of row to delete, and job are in conflict and generate a transaction exception
This change add the notification clean up before resume the jobs, and after deleting digest if necessary.
So When Job are executed, they read tables, find no rows, and exited, without error.