*: postpone drop bundle for truncate/drop partition/drop schema to gc

[lcwangchao]

What problem does this PR solve?

Issue Number: close #29827

Problem Summary:

What is changed and how it works?

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]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• AilinKid
• xhebox

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.

[lcwangchao]

/run-check_dev_2

[AilinKid]

LGTM

[xhebox]

While it is possible to do so, I want to learn that why do you want to postpone the deletion to gc?

[lcwangchao]

While it is possible to do so, I want to learn that why do you want to postpone the deletion to gc?

I'm completing the missing cases for #28687 . But I think the reasons is:

1. Deleting rules when dropping may cause the reschedule of PD. I'm not sure if it'll introduce some extra cost.
2. Users may still expect their data fits the placement rule, even it is dropped. For example: compliance
3. Users can still access deleted data even if it is deleted like stale read. At this time they still want the data fits the placement rule for some reason like isolation.

[xhebox]

/merge

[ti-chi-bot]

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

Commit hash: cd97a2c

[ti-chi-bot]

@lcwangchao: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

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.

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.