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

*: Allow Point_Get during DDL with Global Index #56382

Merged
merged 18 commits into from
Oct 25, 2024

Conversation

mjonss
Copy link
Contributor

@mjonss mjonss commented Sep 27, 2024

What problem does this PR solve?

Issue Number: ref #55819 , ref #45133 , close #56819

Problem Summary:
During DDL that affects Global Index, the PointGet access method is blocked, which may cause temporary bad query plans during partitioning management commands, like DROP/TRUNCATE/REORGANIZE PARTITION.

What changed and how does it work?

Allow PointGet, by filter away the partitions that should not be seen (like when the cleanup of the global index is ongoing).

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. sig/planner SIG: Planner labels Sep 27, 2024
Copy link

tiprow bot commented Sep 27, 2024

Hi @mjonss. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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 kubernetes-sigs/prow repository.

Copy link

codecov bot commented Sep 27, 2024

Codecov Report

Attention: Patch coverage is 93.91304% with 7 lines in your changes missing coverage. Please review.

Project coverage is 57.4851%. Comparing base (7ce5bd7) to head (fdbae50).
Report is 4 commits behind head on master.

Additional details and impacted files
@@                Coverage Diff                @@
##             master     #56382         +/-   ##
=================================================
- Coverage   73.3565%   57.4851%   -15.8714%     
=================================================
  Files          1636       1785        +149     
  Lines        453398     652320     +198922     
=================================================
+ Hits         332597     374987      +42390     
- Misses       100440     252093     +151653     
- Partials      20361      25240       +4879     
Flag Coverage Δ
integration 39.5727% <62.1621%> (?)
unit 72.4745% <74.7747%> (-0.0967%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
dumpling 52.9478% <ø> (ø)
parser ∅ <ø> (∅)
br 62.4134% <ø> (+16.3807%) ⬆️

// session should not see (may be duplicate errors on insert/update though)
// For example during truncate or drop partition.
func (pi *PartitionInfo) IDsInDDLToIgnore() []int64 {
// TODO:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are multiple PRs/enhancements that will build upon this, especially for DROP and TRUNCATE partition.

@mjonss
Copy link
Contributor Author

mjonss commented Sep 28, 2024

/retest

Copy link

tiprow bot commented Sep 28, 2024

@mjonss: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

@mjonss
Copy link
Contributor Author

mjonss commented Sep 28, 2024

Splitted this part from #55819 since it can be reviewed separately.

pkg/ddl/partition.go Outdated Show resolved Hide resolved
pkg/planner/core/find_best_task.go Show resolved Hide resolved
pkg/planner/core/find_best_task.go Show resolved Hide resolved
pkg/planner/core/find_best_task.go Show resolved Hide resolved
@ti-chi-bot ti-chi-bot bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 18, 2024
@ti-chi-bot ti-chi-bot bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 25, 2024
@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Oct 25, 2024
@mjonss
Copy link
Contributor Author

mjonss commented Oct 25, 2024

/retest

Copy link

tiprow bot commented Oct 25, 2024

@mjonss: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot bot added the ok-to-test Indicates a PR is ready to be tested. label Oct 25, 2024
@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Oct 25, 2024
Copy link

ti-chi-bot bot commented Oct 25, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-10-25 10:53:56.700718929 +0000 UTC m=+1549.539874470: ☑️ agreed by Defined2014.
  • 2024-10-25 11:19:17.869087724 +0000 UTC m=+3070.708243270: ☑️ agreed by winoros.

@mjonss mjonss added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 25, 2024
@mjonss mjonss removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 25, 2024
@mjonss
Copy link
Contributor Author

mjonss commented Oct 25, 2024

/retest

2 similar comments
@mjonss
Copy link
Contributor Author

mjonss commented Oct 25, 2024

/retest

@mjonss
Copy link
Contributor Author

mjonss commented Oct 25, 2024

/retest

Copy link

ti-chi-bot bot commented Oct 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Defined2014, tangenta, winoros

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added approved needs-cherry-pick-release-8.4 Should cherry pick this PR to release-8.4 branch. labels Oct 25, 2024
@mjonss
Copy link
Contributor Author

mjonss commented Oct 25, 2024

/retest

@ti-chi-bot ti-chi-bot bot merged commit 33c30ee into pingcap:master Oct 25, 2024
26 checks passed
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-8.4: #56849.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-8.4 Should cherry pick this PR to release-8.4 branch. ok-to-test Indicates a PR is ready to be tested. release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Row not found for Global Index during DeleteOnly state of Reorganize Partition
6 participants