*: Fix invalid memory access when shutting down

[JaySon-Huang]

What problem does this PR solve?

Issue Number: close #8408

Problem Summary:

There is an invalid memory access. This is because the logging system is already closed

What is changed and how it works?

When sub_root_of_query_storage_task_mem_trackers and its children are destructoring, it means the process is shutting down and the logging system is stopped.

Suppress the logging of these memory trackers.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  • Add a line after store_idnet is got to mock an exception thrown and tiflash stopped throw Exception("Mock exception thrown");
    

    tiflash/dbms/src/Server/Server.cpp

    Lines 1707 to 1716 in 3d3a5f1

    	if (store_ident)
    	{
    	RUNTIME_ASSERT(
    	store_id == store_ident->store_id(),
    	log,
    	"store id mismatch store_id={} store_ident.store_id={}",
    	store_id,
    	store_ident->store_id());
    	}
    	if (global_context->getSharedContextDisagg()->isDisaggregatedComputeMode())

• 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

[JaySon-Huang]

/run-all-tests

[JinheLin]

This header seems unnecessary.

[JaySon-Huang]

it is need by struct TemporarilyDisableMemoryTracker : private boost::noncopyable in line 192

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-11-22 09:08:08.620775748 +0000 UTC m=+395317.286001944: ☑️ agreed by Lloyd-Pottiger.
• 2023-11-22 09:14:11.336662814 +0000 UTC m=+395680.001889009: ☑️ agreed by JinheLin.

[JaySon-Huang]

/approve

[ti-chi-bot]

@JaySon-Huang: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

• Currently the CI jobs are not prow job style, we need it to notify Jenkins server to run them.
• 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.

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]

[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

[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

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.

[JaySon-Huang]

/run-all-tests

[ti-chi-bot]

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