-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11626. Optimize ResourceManager's operations on Zookeeper metadata #6577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
💔 -1 overall
This message was automatically generated. |
| break; | ||
| } | ||
| } catch (KeeperException.NoNodeException nne){ | ||
| if(!exists(path)){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here, You just need to focus on the NoNodeException of REMOVE action
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. I've modified and tested this.
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
Hi @XbaoWu Please submit PR to trunk first, if approved and committed to trunk, then backport to other active branches if necessary. |
Okay, thank you for your reminder |
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?