YARN-11401 Separate ApllicationMaster cleanup events and launcher events into different resource pools #5241
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.
Currently, there is only one thread pool to handle AM launch and cleanup event in ResourceManager.
We found an issue in our cluster, in some cases, too many cleanup events will block AM launcher event and make it stuck for a long time.
So in this PR, we divide the shared thread pool into two separated ones to handle AM event of different kinds in case that a flood events of cleanup events blocking launcher event for a long time and vice versa, which will badly decay throughput of ResourceManager.