Skip to content
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

Schedule source stages in sequence in FixedSourcePartitionedScheduler #13655

Merged
merged 2 commits into from
Aug 12, 2022

Conversation

sopel39
Copy link
Member

@sopel39 sopel39 commented Aug 12, 2022

Before grouped execution was added, source stages in FixedSourcePartitionedScheduler
were scheduled in sequence. When grouped execution got removed
that logic was lost. This PR restores the logic so that
partitioned queries don't get deadlocked

Description

Is this change a fix, improvement, new feature, refactoring, or other?

fix

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

core (scheduler)

How would you describe this change to a non-technical end user or system administrator?

Prevent queries from deadlocking which was introduced when grouped execution was removed

Related issues, pull requests, and links

Fixes #13652

Documentation

( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Prevent queries on bucketed tables from deadlocking ({issue}`issuenumber`)

Before grouped execution was added, source stages in FixedSourcePartitionedScheduler
were scheduled in sequence. When grouped execution got removed
that logic was lost. This PR restores the logic so that
partitioned queries don't get deadlocked
@sopel39
Copy link
Member Author

sopel39 commented Aug 12, 2022

Failed due #13556

@sopel39
Copy link
Member Author

sopel39 commented Aug 12, 2022

Fails due #13658

@sopel39 sopel39 merged commit 17247b9 into trinodb:master Aug 12, 2022
@sopel39 sopel39 deleted the ks/fix_deadlock branch August 12, 2022 20:33
@sopel39 sopel39 mentioned this pull request Aug 12, 2022
@github-actions github-actions bot added this to the 393 milestone Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Union query may blocked after remove grouped execution
2 participants