You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For more information about this PR, please refer to the following issue: YARN-11626 Optimization of the safeDelete operation in ZKRMStateStore
The NoNodeException clearly indicates that the Znode no longer exists, so if we check again and find that the node does not actually exist, we can safely ignore this exception to avoid triggering a larger impact on the cluster caused by ResourceManager failover.
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
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
For more information about this PR, please refer to the following issue:
YARN-11626 Optimization of the safeDelete operation in ZKRMStateStore
The NoNodeException clearly indicates that the Znode no longer exists, so if we check again and find that the node does not actually exist, we can safely ignore this exception to avoid triggering a larger impact on the cluster caused by ResourceManager failover.
How was this patch tested?
add TestCheckRemoveZKNodeRMStateStore.testSafeDeleteZKNode()
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?