[BugFix] fix be exit probelm (backport #44162) #44216
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I'm doing:
introduced by #42351
https://github.com/StarRocks/StarRocksTest/issues/7060 one of its' problem is be can not exit gracefully:
p (ThreadPool)(0x61600010d780)
What I'm doing:
becase ThreadPool has CoreLocalCounter as member variable, so every ThreadPool have to be released before CoreLocalValueController which is a static single instance. I just reset two ThreadPool which use smart pointer in ExecEnv::destory, so these two thread pools will be released before CoreLocalValueController
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #44162 done by [Mergify](https://mergify.com). ## Why I'm doing: introduced by https://github.com//pull/42351
https://github.com/StarRocks/StarRocksTest/issues/7060 one of its' problem is be can not exit gracefully:
p (ThreadPool)(0x61600010d780)
What I'm doing:
becase ThreadPool has CoreLocalCounter as member variable, so every ThreadPool have to be released before CoreLocalValueController which is a static single instance. I just reset two ThreadPool which use smart pointer in ExecEnv::destory, so these two thread pools will be released before CoreLocalValueController
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: