YARN-11957. Frequent NM Label Updates Cause Longer RM Failover Time#8489
Open
zhangxiping1 wants to merge 2 commits intoapache:trunkfrom
Open
YARN-11957. Frequent NM Label Updates Cause Longer RM Failover Time#8489zhangxiping1 wants to merge 2 commits intoapache:trunkfrom
zhangxiping1 wants to merge 2 commits intoapache:trunkfrom
Conversation
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
In our scenario, the labels of a batch of nodes are updated periodically. After the active RM had been running for a long time, an active-standby switchover was triggered, and the switchover took an unusually long time. By analyzing the logs and jstack information related to the standby RM's transition to active, we found that a core thread, "SchedulerEventDispatcher:Event Processor", had been continuously processing updateNodeLabelsAndQueueResource. The service logs also showed a large number of "REPLACE labels on nodes" messages.