PageStorage: Fix invalid offset after restart

[JaySon-Huang]

What problem does this PR solve?

Issue Number: close #6218

Problem Summary:
Introduce by #6168

The fix can not properly handle the following situation

What is changed and how it works?

• Better handle WriteBatch{ put X, ref Y->X, delete X} inside one WriteBatch (PageDirectory::apply)
  • Previously, we use the same version.sequence inside one WriteBatch
  • Now we increase the version.sequence inside one WriteBatch, and atomically increase the PageDirectory.sequence at last
• Check whether the page is deleted or not when preparing full GC
  • If the page itself is deleted (even still being ref by another id), then we won't rewrite it
  • If the page is a reference to another id, and is not deleted, we will rewrite the data with ref-id in full GC
    • If the ref-page is not deleted before full GC commits new entry, we will rewrite the ref-page into a normal page with { upsert-entry } and decrease the ref-count of origin-id
    • If the ref-page is deleted before full GC commits new entry, we will rewrite the ref-page into a normal page with { upsert-entry, delete_ver}

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  Run chbenchmark with warehouse 100 and tiflash random kill. TiFlash can restart normally.
• 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:

• flowbehappy
• lidezhu

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.

Details

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

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/cc @lidezhu @flowbehappy @hehechen

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-all-tests

[lidezhu]

LGTM

[JaySon-Huang]

/run-all-tests

[flowbehappy]

LGTM

[JaySon-Huang]

/merge

[ti-chi-bot]

@JaySon-Huang: 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.

Details

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]

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

Details

Commit hash: d1cad72

[ti-chi-bot]

@JaySon-Huang: 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.

Details

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.