This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Fixes start API not setting FAILED metadata to RETRY. Also fixes bug … #347
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.
…with releaseLock not correclty releasing an updated lock
Issue #, if available:
Description of changes:
Previously Start API was setting everything to STARTED no matter what, now it will:
Skip updating any metadata that is already in: [STARTED, INIT, RETRY]
Set these to STARTED: [FINISHED, STOPPED]
And set FAILED to RETRY
There was also a bug with runRollupJob where we constantly renewed the lock which is updating the seqNo/primaryTerm. So once a job that was running fails or completes the outside releaseLock will fail because of version conflict which means then any potential next execution from a retry call needs to wait for the ttl to expire. This adds release locks inside the runRollupJob where needed, although not the cleanest solution with it littered in a few places. Will go back later and see how we can clean up that part (i.e. return lock for outside release or something).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.