[
https://issues.apache.org/jira/browse/HDFS-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196218#comment-16196218
]
Elek, Marton commented on HDFS-12611:
-------------------------------------
Test failures are not related. There are unit test for SCMCli but it's turned
off. I tried to turn it on locally and the connectivity (which is fixed by the
patch) is worked. (there was an error with the container delete but it's not
related to this patch)
> Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
> --------------------------------------------------------------------------
>
> Key: HDFS-12611
> URL: https://issues.apache.org/jira/browse/HDFS-12611
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: HDFS-7240
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Attachments: HDFS-12611-HDFS-7240.0001.patch
>
>
> During tests I found that I can't use SCM CLI in multi-node environment:
> {code}
> 2017-10-06 21:00:25 INFO Client:939 - Retrying connect to server:
> 0.0.0.0/0.0.0.0:9860. Already tried 0 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> 2017-10-06 21:00:26 INFO Client:939 - Retrying connect to server:
> 0.0.0.0/0.0.0.0:9860. Already tried 1 time(s); retry policy is
> RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000
> MILLISECONDS)
> {code}
> The reason is that we should use the OZONE_SCM_CLIENT_ADDRESS_KEY instead of
> OZONE_SCM_BIND_HOST_KEY as the bind host could be 0.0.0.0 and the
> SCM_CLIENT_ADDRESS contains the external address of the SCM server (in my
> case scm was on a different host)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
