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

fix bug that ExchangeReceiver is not cancelled if exception happens in union/agg block input stream #4285

Merged
merged 8 commits into from
Mar 15, 2022

Conversation

windtalker
Copy link
Contributor

@windtalker windtalker commented Mar 15, 2022

Signed-off-by: xufei [email protected]

What problem does this PR solve?

Issue Number: ref #4229

Problem Summary:

some backgrounds:

  • For every BlockInputStream, there is a cancel(bool kill) method to cancel the current and all its children input streams.
  • In UnionBlockInputStream/ParallelAggregatingBlockInputStream, if some exception happens during processor.process(), it will cancel the BlockInputStream in processor. However, it use silent cancel(false) to do this, which will be ignored by TiRemteBlockInputStream, so the remote_reader in TiRemoteBlockInputStream is not cancelled by cancel(false).
  • Due to the implementation of cancel, if a input stream is cancel once, all the subsequent cancels(including cancel(true)) will be ignored.
  • MPPTask will use cancel(true) to cancel its BlockInputStream, and all the remote_reader in TiRemoteInputStream

problem
If a input stream is cancelled due to exception in UnionBlockInputStream/ParallelAggregatingBlockInputStream, Cancel query can not cancel this input stream anymore, leaving remote_reader un-cancelled, which may block the MPP query forever.

What is changed and how it works?

In UnionBlockInputStream/ParallelAggregatingBlockInputStream, if some exception happens during processor.process(), use cancel(true) to cancel the BlockInputStream in processor.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

None

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Mar 15, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • bestwoody
  • fuzhe1989

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 15, 2022
@bestwoody
Copy link
Contributor

A little confuse about background "Due to the implementation of cancel, if a input stream is cancel once, all the subsequent cancels(including cancel(true)) will be ignored." . How input stream ensure to be canceled at most call once.

@windtalker
Copy link
Contributor Author

A little confuse about background "Due to the implementation of cancel, if a input stream is cancel once, all the subsequent cancels(including cancel(true)) will be ignored." . How input stream ensure to be canceled at most call once.

 if (!is_cancelled.compare_exchange_strong(old_val, true, std::memory_order_seq_cst, std::memory_order_relaxed))
        return;

@bestwoody
Copy link
Contributor

is_cancelled

oh, I see

Copy link
Contributor

@bestwoody bestwoody left a comment

Choose a reason for hiding this comment

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

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Mar 15, 2022
dbms/src/DataStreams/UnionBlockInputStream.h Outdated Show resolved Hide resolved
dbms/src/DataStreams/UnionBlockInputStream.h Outdated Show resolved Hide resolved
dbms/src/DataStreams/UnionBlockInputStream.h Show resolved Hide resolved
/// can not cancel parent inputStream or the exception might be lost
parent.processor.cancel(false); /// Does not throw exceptions.
/// kill the processor so ExchangeReceiver will be closed
parent.processor.cancel(true);
Copy link
Contributor

Choose a reason for hiding this comment

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

why not also do parent.processor.cancel(true) in handleException?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK

@ti-chi-bot ti-chi-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 15, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Mar 15, 2022
@windtalker
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

@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 /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 2feaf00

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Mar 15, 2022
@sre-bot
Copy link
Collaborator

sre-bot commented Mar 15, 2022

Coverage for changed files

too many lines from llvm-cov, please refer to full report instead

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
16923      9503             43.85%    190683  96482        49.40%

full coverage report (for internal network access only)

@windtalker
Copy link
Contributor Author

/run-all-tests

@sre-bot
Copy link
Collaborator

sre-bot commented Mar 15, 2022

Coverage for changed files

too many lines from llvm-cov, please refer to full report instead

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
16923      9502             43.85%    190681  96489        49.40%

full coverage report (for internal network access only)

@sre-bot
Copy link
Collaborator

sre-bot commented Mar 15, 2022

Coverage for changed files

too many lines from llvm-cov, please refer to full report instead

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
16923      9503             43.85%    190681  96469        49.41%

full coverage report (for internal network access only)

@ti-chi-bot ti-chi-bot merged commit 752793b into pingcap:master Mar 15, 2022
ti-chi-bot pushed a commit to ti-chi-bot/tiflash that referenced this pull request Mar 15, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4289.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #4290.

@windtalker windtalker mentioned this pull request Mar 16, 2022
12 tasks
JaySon-Huang pushed a commit to JaySon-Huang/tiflash that referenced this pull request Mar 17, 2022
windtalker added a commit that referenced this pull request Apr 1, 2022
windtalker added a commit to windtalker/tiflash that referenced this pull request Apr 14, 2022
windtalker added a commit that referenced this pull request Apr 14, 2022
ti-chi-bot added a commit that referenced this pull request Apr 22, 2022
ti-chi-bot added a commit that referenced this pull request Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants