Release WF slot on UnableToAcquireLockException #1871
Merged
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.
A user noticed that if their workflow task failed with
UnableToAcquireLockException
their worker would not be able to shutdown. Root cause was onUnableToAcquireLockException
we didn't calltask.getCompletionCallback().apply();
because the exception was outside thefinally
block.Note: this will change the timing of
WORKFLOW_TASK_EXECUTION_TOTAL_LATENCY
to include the time waiting for the run lock, but this metric is java specific and is undocumented, and arguably should include the run lock.close #1870