-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[SPARK-57638][SQL] Avoid busy-waiting in Declarative Pipelines flow resolution #56700
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e348463
[SPARK-57638][SQL] Avoid busy-waiting in Declarative Pipelines flow r…
LuciferYang 3e138a4
[SPARK-57638][SQL][FOLLOWUP] Explain why the take() branch guards on …
LuciferYang 4b86d97
[SPARK-57638][SQL][FOLLOWUP] Add deterministic tests for resolution w…
LuciferYang 70268c3
[SPARK-57638][SQL][FOLLOWUP] Make the re-queue test deterministic and…
LuciferYang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: the
else if (outstanding > 0)guard is effectively always true when reached. Control only reaches it when the if is false, i.e.outstanding >= batchSize || queue.isEmpty. SincebatchSize >= 1, the first disjunct implies outstanding > 0; and if the queue is empty the loop invariant guarantees outstanding > 0. So it could just be a plainelse?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, but the guard is needed - a plain
elsewould deadlock the last iteration. The reasoning misses that thepoll()drain loop runs after the loop-condition check and mutatesoutstanding. The invariantoutstanding > 0 || queue.nonEmptyonly holds at the top of the loop; by the time we reach this branch, the drain may have reaped the last in-flight tasks and takenoutstandingto 0 while the queue is already empty. In that case theifis false (empty queue) and there is nothing left to wait for -take()would block forever. Theoutstanding > 0guard lets the loop fall through so the next condition check (0 > 0 || empty) exits cleanly. I added a comment spelling this out.