YARN-11251. Separate ThreadPool for AMLauncher Launch and Clean Events #8208
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.
Description of PR
When hadoop cluster running on cloud , uses spot instance and AM is launched on one of those instances. When these instances are removed then we have observed too many AM Launch Failures due to Token Expired or Container Liveliness Expiry when AM Launch Threads are busy retrying to connect to AM Host (Spot Instances) which are down. Having Separate ThreadPools for both Cleanup and Launch will reduce the AM Launch failures.
Token Expired
Container Liveliness Expiry
Associated ticket :- YARN-11251
How was this patch tested?
This patch is tested in EMR cluster where 1 master node and 1 core nodes , and 2 tasks nodes , task nodes are spot instances , we launched an AM in one of the task node and bring it down , This replicate the following senerio
TODO :- unit test need to be added
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?