HDDS-5116. Secure datanode/OM may exit if it cannot connect to SCM.#2162
Merged
bshashikant merged 4 commits intoapache:masterfrom Apr 21, 2021
Merged
HDDS-5116. Secure datanode/OM may exit if it cannot connect to SCM.#2162bshashikant merged 4 commits intoapache:masterfrom
bshashikant merged 4 commits intoapache:masterfrom
Conversation
bshashikant
approved these changes
Apr 21, 2021
Contributor
|
Thanks @bharatviswa504 for the contribution. |
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.
What changes were proposed in this pull request?
Following changes are done:
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5116
How was this patch tested?
Tested manually, started OM/DN before SCM Startup and they are retrying more than default 15 retry count.
docker-compose up --build om1 datanode1
After some time greater than default retry completed start scm
docker-compose up --build scm1.org scm2.org scm3.org
om1_1 | 2021-04-20 07:15:09,675 [main] INFO retry.RetryInvocationHandler: com.google.protobuf.ServiceException: java.net.NoRouteToHostException: No Route to Host from om1/172.25.0.111 to scm1.org:9863 failed on socket timeout exception: java.net.NoRouteToHostException: No route to host; For more details see: http://wiki.apache.org/hadoop/NoRouteToHost, while invoking $Proxy31.send over nodeId=scm1,nodeAddress=scm1.org/172.25.0.116:9863 after 45 failover attempts. Trying to failover after sleeping for 2000ms.datanode1_1 | 2021-04-20 07:15:35,048 [main] INFO retry.RetryInvocationHandler: com.google.protobuf.ServiceException: java.net.ConnectException: Call From 9cb343c107ed/172.25.0.102 to scm3.org:9961 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused, while invoking $Proxy17.submitRequest over nodeId=scm3,nodeAddress=scm3.org/172.25.0.118:9961 after 35 failover attempts. Trying to failover after sleeping for 2000ms.And once SCM is booted up DN and OM are able to successfully startup.