Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Ignore finished tasks when computing memory usage for stage #11801

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

Merged
merged 2 commits into from
Apr 6, 2022

Conversation

losipiuk
Copy link
Member

@losipiuk losipiuk commented Apr 5, 2022

Description

Ignore finished tasks when computing memory usage for stage.
Without the fix stage level statistics for peak and current memory were off when task retries happened.

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

bugfix

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

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

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

# Engine
* Fix stage memory statistics reporting for queries running with `retry-policy` set to `TASK`. ({issue}`11801`)

@cla-bot cla-bot bot added the cla-signed label Apr 5, 2022
@losipiuk losipiuk requested review from linzebing and arhimondr April 5, 2022 15:44
@losipiuk losipiuk force-pushed the lo/fix-used-memory-accounting branch from 466307a to a84708a Compare April 6, 2022 08:16
@losipiuk losipiuk merged commit 9a35dfc into trinodb:master Apr 6, 2022
@github-actions github-actions bot added this to the 376 milestone Apr 6, 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.

2 participants