Disagg: Fix the issue that lifetime of read-snapshots in WN may be longer than expected (#9297)

[ti-chi-bot]

This is an automated cherry-pick of #9297

What problem does this PR solve?

Issue Number: close #9298

Problem summary:
Snapshot of each SegmentReadTask will be released after FetchDisaggPages is called. But for some segments with no ColumnFileTiny or ColumnFileInMemory to fetch, FetchDisaggPages will never be called.

What is changed and how it works?

1. In WN, release snapshots of SegmentReadTasks that do not have ColumnFileTiny and ColumnFileInMemory.
2. In CN, no matter all ColumnFileTinys and ColumnFileInMemorys are cached or not, call FetchDisaggPages to release snapshot in WN.

Notes:

• From v8.1.0, CN need to fetch ColumnFileTiny and ColumnFileInMemory.
• In v7.5.0, CN only need to fetch ColumnFileTiny.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  • Run CH-Benchmark workload and check the snapshot metrics.
• 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 the issue that lifetime of read-snapshots in write-nodes may be longer than expected in disaggregated-mode.

[JaySon-Huang]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-03 06:09:01.651151896 +0000 UTC m=+338266.169204822: ☑️ agreed by JinheLin.
• 2024-09-03 06:15:13.768906657 +0000 UTC m=+338638.286959583: ☑️ agreed by JaySon-Huang.

[JaySon-Huang]

/run-all-tests

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, JinheLin, Lloyd-Pottiger

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:

• OWNERS [JaySon-Huang,JinheLin,Lloyd-Pottiger]

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

[JaySon-Huang]

/run-integration-test

[ti-chi-bot]

@ti-chi-bot: 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

trigger some heavy tests which will not run always when PR updated.

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.