Storages: Avoid SegmentReadTaskScheduler blocking the adding threads and ignore empty SegmentReadTaskPool

[JinheLin]

What problem does this PR solve?

Issue Number: close #9024

Problem Summary:

• The thead of SegmentReadTaskScheduler may running with no segment to be scheduled unexpectly and holds the mutex that blocking the adding threads.

What is changed and how it works?

• Manual cherry-pick of Storages: refine SegmentReadTaskScheduler #8557 to fix the problem above because this PR will may the scheduler sleep if there is no segment need too be schedule.
• Ignore SegmentReadTaskPool with no segment.

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 the bug that executing queries on partitioned table with empty partition may timeout

[JaySon-Huang]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, 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,Lloyd-Pottiger]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-05-08 03:15:44.332405393 +0000 UTC m=+1018298.089540966: ☑️ agreed by JaySon-Huang.
• 2024-05-08 03:52:34.122537409 +0000 UTC m=+1020507.879672975: ☑️ agreed by Lloyd-Pottiger.

[ti-chi-bot]

@JinheLin: 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.

[Lloyd-Pottiger]

/run-integration-test