[jira] [Updated] (HDFS-12611) Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
[
https://issues.apache.org/jira/browse/HDFS-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated HDFS-12611:
--
Component/s: ozone
> 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
> Components: ozone
>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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12611) Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
[
https://issues.apache.org/jira/browse/HDFS-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated HDFS-12611:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
The failed tests are unrelated, the failed tests are unrelated. Thansk [~elek]
for the contribution!
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12611) Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
[
https://issues.apache.org/jira/browse/HDFS-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDFS-12611:
Description:
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)
was:
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)
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12611) Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
[
https://issues.apache.org/jira/browse/HDFS-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDFS-12611:
Status: Patch Available (was: Open)
> 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 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12611) Ozone: SCM Cli: Use the hostname of SCM server instead of the bind address
[
https://issues.apache.org/jira/browse/HDFS-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDFS-12611:
Attachment: HDFS-12611-HDFS-7240.0001.patch
To test:
Do a full build and startup a cluster:
dev-support/compose/ozone/
docker-compose up -d
the scmcli should work from different host (for example from the ksm server):
docker exec -it ozone_ksm_1 bash
hdfs scm -container -list -count 10
Without the patch it works only from the scm server.
> 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 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
