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

[Backport] Segregate advance and advanceUninterruptibly flow in postJoinCursor to allow for interrupts in advance #15278

Merged

Conversation

LakshSingla
Copy link
Contributor

Backport of #15222 to 28.0.0.

…o allow for interrupts in advance (apache#15222)

Currently advance function in postJoinCursor calls advanceUninterruptibly which in turn keeps calling baseCursor.advanceUninterruptibly until the post join condition matches, without checking for interrupts. This causes the CPU to hit 100% without getting a chance for query to be cancelled.

With this change, the call flow of advance and advanceUninterruptibly is separated out so that they call baseCursor.advance and baseCursor.advanceUninterruptibly in them, respectively, giving a chance for interrupts in the former case between successive calls to baseCursor.advance.
@AmatyaAvadhanula AmatyaAvadhanula merged commit cfd9761 into apache:28.0.0 Nov 2, 2023
77 checks passed
@LakshSingla LakshSingla deleted the backport-15222-to-28.0.0 branch November 2, 2023 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants