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

ddl: fix concurrent column type changes(with changing data) that cause schema and data inconsistencies #31051

Merged
merged 5 commits into from
Dec 28, 2021

Conversation

zimulala
Copy link
Contributor

@zimulala zimulala commented Dec 27, 2021

What problem does this PR solve?

Issue Number: close #31048

Problem Summary:

For column type changes, the column ID is changed if it is lossy.

If both sessions perform lossy column type changes((like modify column c int -> char)) simultaneously

  1. Connection1: execute DDL1, it will change column ID (ID :1-> ID :2)

  2. Connection2: execute DDL2. After DDL1 enters the DDL job queue and is not executed, then DDL2 enters the job queue.

  3. After DDL1 is executed successfully, DDL2 considers that the column is not lossy(char -> char), so it does not change the column ID, which is the old id:1. So id:1 overwrites id:2.

After DDL2 is completed, the column ID is still the original id:1 instead of the correct id:2.

Because the column ID was changed incorrectly, the schema could not match the data, resulting in decode failure when reading data.

What is changed and how it works?

In step 3, we check that the ID of the modified column is the same as the ID of the original column.

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

Fix concurrent column type changes(with changing data) that cause schema and data inconsistencies.

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 27, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • AilinKid
  • tangenta

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 Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Dec 27, 2021
@sre-bot
Copy link
Contributor

sre-bot commented Dec 27, 2021

Copy link
Contributor

@AilinKid AilinKid 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 Dec 27, 2021
@@ -1062,6 +1062,54 @@ func (s *testStateChangeSuite) TestParallelAlterModifyColumn(c *C) {
s.testControlParallelExecSQL(c, sql, sql, f)
}

func (s *testStateChangeSuite) TestParallelAlterModifyColumnWithData(c *C) {
Copy link
Member

Choose a reason for hiding this comment

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

Can we add more tests about concurrent alter table? For example, random test.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Could you give an example of this random test? I don't think it's appropriate to add it here.

@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 Dec 27, 2021
ddl/column.go Outdated Show resolved Hide resolved
@zimulala
Copy link
Contributor Author

PTAL @wjhuang2016 @bb7133

@zimulala
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

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

Commit hash: 7f98a78

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 28, 2021
@ti-chi-bot ti-chi-bot merged commit 4ca3b02 into pingcap:master Dec 28, 2021
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Dec 28, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.1 in PR #31069

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Dec 28, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.2 in PR #31070

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Dec 28, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.3 in PR #31071

@zimulala zimulala deleted the zimuxia/ctc-p branch December 28, 2021 06:01
ti-chi-bot pushed a commit that referenced this pull request Feb 22, 2022
ti-chi-bot pushed a commit that referenced this pull request Feb 22, 2022
ti-chi-bot pushed a commit that referenced this pull request Apr 12, 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.1 needs-cherry-pick-release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/sql-infra SIG: SQL Infra 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. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Concurrent Column Type Change would cause inconsistent schema and data
8 participants