hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-12611) Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
Date Fri, 06 Oct 2017 21:44:00 GMT
Elek, Marton created HDFS-12611:
-----------------------------------

             Summary: 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


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 should contain the external address
(in my case scm was on a different host)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org


Mime
View raw message