-
Notifications
You must be signed in to change notification settings - Fork 409
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
avoid tiflash crash when query is killed #3434
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
if (current_memory_tracker != memory_tracker) | ||
current_memory_tracker = memory_tracker; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems be unnecessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just a double check, if the current_memory_tracker
is already memory_tracker
, do not need to overwrite current_memory_tracker
dbms/src/Flash/Mpp/MPPTask.h
Outdated
/// store io in MPPTask to keep the life cycle of memory_tracker for the current query | ||
/// BlockIO contains some information stored in Context and DAGContext, so need deconstruct it before Context and DAGContext | ||
BlockIO io; | ||
/// The inputStreams should be released in the destructor of BlockIO, since DAGContext contains some reference to inputStreams, so it need | ||
/// to be destructed before BlockIO | ||
std::unique_ptr<DAGContext> dag_context; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update the dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
6f5972e
to
c318320
Compare
c318320
to
cdd99c0
Compare
/merge |
@windtalker: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
This pull request has been accepted and is ready to merge. Commit hash: cdd99c0
|
In response to a cherrypick label: new pull request created: #3448. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3449. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3450. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3451. |
What problem does this PR solve?
Issue Number: close #3401
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
Root cause:
The memory tracker is destructed before it is used
2. NPE by join
The exception happens during hash table build is lost, so hash table probe begins when the hash table is still in build stage.
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note