symious commented on PR #3409: URL: https://github.com/apache/ozone/pull/3409#issuecomment-1125956137
@JacksonYao287 Sure, thanks for the review. In https://github.com/apache/ozone/pull/2765#issuecomment-952091699, the concern I think is the misconfig of client side might trigger some dead loops, so an address was prefered to add instead of only OMNodeId. In the latest commit of this PR, the `OMNotLeaderException` includes the following information: 1. raftPeerId 2. raftLeaderId 3. raftLeaderAddress An example of this exception message would be ```org.apache.hadoop.ozone.om.exceptions.OMNotLeaderException: OM:omNode-3 is not the leader. Suggested leader is OM:omNode-1/127.0.0.1``` , when client received this exception, he should try the address first, only if the address is empty should he try to check the raftLeaderId we suggested. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
