v3: fix dependency checkpoint race #1171
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.
This affects
Task.triggerAndWait()
andTask.batchTriggerAndWait()
. A race condition could result where the dependency completes just before the checkpoint does.If the timing is just right, the created checkpoint causes the resume message from dependency completion to be ACKed. This means the parent task stays stuck in the frozen state. Another issues is that even if the resume comes through, there's won't be a running task to send it to, as checkpoint completion also results in parent task termination.
The fix involves checking for dependency completion after creating the checkpoint event, and only ACKing if the dependency hasn't completed yet. Also, if the dependency has completed, we will keep the parent task alive so it can resume immediately.