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

Fail query if we cannot allocate enough memory #11875

Merged

Conversation

losipiuk
Copy link
Member

@losipiuk losipiuk commented Apr 8, 2022

On top of On top of #11802; just review 3 top commits

Description

Fail whole query if for a retry node allocator is not capable of allocating more memory than was reached in peak during previous attempt of retried task.

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

Improvement

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

Core engine

Related issues, pull requests, and links

Documentation

(x) 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

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

@cla-bot cla-bot bot added the cla-signed label Apr 8, 2022
@losipiuk losipiuk force-pushed the lo/kill-task-when-no-more-memory-avail branch from 705cbb1 to 5204b66 Compare April 11, 2022 13:22
@losipiuk
Copy link
Member Author

On top of #11802

@losipiuk losipiuk marked this pull request as ready for review April 11, 2022 13:30
@losipiuk losipiuk requested review from arhimondr and linzebing April 11, 2022 13:59
@losipiuk losipiuk force-pushed the lo/kill-task-when-no-more-memory-avail branch from 5204b66 to 47f49e3 Compare April 12, 2022 10:02
@losipiuk
Copy link
Member Author

rebased

@losipiuk losipiuk force-pushed the lo/kill-task-when-no-more-memory-avail branch from 47f49e3 to d38bae3 Compare April 12, 2022 10:13
…llocator

It is convenient to have those two coupled so we can make use of workers
memory pool information within ExponentialGrowthPartitionMemoryEstimator
@losipiuk losipiuk force-pushed the lo/kill-task-when-no-more-memory-avail branch from d38bae3 to b76b141 Compare April 12, 2022 14:32
@losipiuk losipiuk merged commit 835b0dd into trinodb:master Apr 12, 2022
@github-actions github-actions bot added this to the 377 milestone Apr 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.

3 participants