Skip to content

Fix possible StackOverflowError in BufferingSplitSource#19369

Merged
raunaqmorarka merged 2 commits intotrinodb:masterfrom
raunaqmorarka:fix-so
Nov 9, 2023
Merged

Fix possible StackOverflowError in BufferingSplitSource#19369
raunaqmorarka merged 2 commits intotrinodb:masterfrom
raunaqmorarka:fix-so

Conversation

@raunaqmorarka
Copy link
Copy Markdown
Member

Description

Additional context and related issues

Fixes #15073

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could it end up being active loop?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code is added to prevent a problem of waiting forever because of splits being produced after a future is already done.
If there is a problem with some test usage, then the test will fail or loop forever.

Avoid chaning futures on a directExecutor by submitting
requests for fetching splits to a separte thread pool instead
@raunaqmorarka raunaqmorarka merged commit bebc42f into trinodb:master Nov 9, 2023
@raunaqmorarka raunaqmorarka deleted the fix-so branch November 9, 2023 19:34
@github-actions github-actions bot added this to the 433 milestone Nov 9, 2023
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.

StackOverflowError possible BufferingSplitSource when connector generates large number of splits

5 participants