Skip to content

gc_worker: Do not do delete_files_in_range on lock cf which has potential risk to affect data correctness#18092

Merged
ti-chi-bot[bot] merged 3 commits intotikv:masterfrom
MyonKeminta:m/do-not-delete-files-in-range-on-lock-cf
Jan 13, 2025
Merged

gc_worker: Do not do delete_files_in_range on lock cf which has potential risk to affect data correctness#18092
ti-chi-bot[bot] merged 3 commits intotikv:masterfrom
MyonKeminta:m/do-not-delete-files-in-range-on-lock-cf

Conversation

@MyonKeminta
Copy link
Contributor

What is changed and how it works?

Issue Number: Close #18091

What's Changed:

gc_worker: Do not do delete_files_in_range on lock cf which has potential risk to affect data correctness

Related changes

  • PR to update pingcap/docs/pingcap/docs-cn:
  • Need to cherry-pick to the release branch

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

Release note

None

…to affect data correctness

Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com>
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the dco. do-not-merge/needs-triage-completed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 6, 2025
Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com>
@ti-chi-bot ti-chi-bot bot added needs-1-more-lgtm Indicates a PR needs 1 more LGTM. approved labels Jan 8, 2025
Copy link
Collaborator

@cfzjywxk cfzjywxk 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
Copy link
Contributor

ti-chi-bot bot commented Jan 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, zyguan

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

The pull request process is described here

Details 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 lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jan 13, 2025
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jan 13, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-01-08 15:18:16.655386481 +0000 UTC m=+366839.944218186: ☑️ agreed by zyguan.
  • 2025-01-13 02:23:15.207145779 +0000 UTC m=+752338.495977484: ☑️ agreed by cfzjywxk.

@cfzjywxk
Copy link
Collaborator

@MyonKeminta Is it necessary to pick it to the release branch?

@ti-chi-bot ti-chi-bot bot merged commit 7a5a4a1 into tikv:master Jan 13, 2025
1 check passed
@ti-chi-bot ti-chi-bot bot added this to the Pool milestone Jan 13, 2025
@MyonKeminta MyonKeminta deleted the m/do-not-delete-files-in-range-on-lock-cf branch January 14, 2025 06:40
@MyonKeminta
Copy link
Contributor Author

@MyonKeminta Is it necessary to pick it to the release branch?

@cfzjywxk I think it's not very necessary as the possibility it causes problem is too low.

@ti-chi-bot ti-chi-bot bot added the needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. label Feb 5, 2025
@ti-chi-bot
Copy link
Member

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

@ti-chi-bot ti-chi-bot bot removed the needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. label Feb 5, 2025
xzhangxian1008 pushed a commit to xzhangxian1008/tikv that referenced this pull request Feb 8, 2025
…tial risk to affect data correctness (tikv#18092)

close tikv#18091

gc_worker: Do not do delete_files_in_range on lock cf which has potential risk to affect data correctness

Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Signed-off-by: xzhangxian1008 <xzhangxian@foxmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved dco-signoff: yes Indicates the PR's author has signed the dco. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UnsafeDestroyRange should not do delete_files_in_range for the lock CF

4 participants