[jira] [Commented] (HDDS-2229) ozonefs paths need host and port information for non HA environment
[ https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943175#comment-16943175 ] Siyao Meng commented on HDDS-2229: -- [~nmaheshwari] As it turns out the reason for the failure is that hdfs shell didn't have ozone-site.xml in its config path. Therefore, it couldn't read the ozone.om.address config, which is required when the host and port is ignored. So this is not a bug on the code side. Anyway, thanks for filing this. Closing this jira now. > ozonefs paths need host and port information for non HA environment > --- > > Key: HDDS-2229 > URL: https://issues.apache.org/jira/browse/HDDS-2229 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Namit Maheshwari >Priority: Major > > > For non HA environment ozonefs path need to have host and port info, like > below: > o3fs://bucket.volume.om-host:port/key > Whereas, for HA environments the path will change to use nameservice like > below: > o3fs://bucket.volume.ns1/key > This will create ambiguity. User experience should be the same irrespective > of the usage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-2229) ozonefs paths need host and port information for non HA environment
[
https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943104#comment-16943104
]
Namit Maheshwari commented on HDDS-2229:
Discussed this with [~smeng]
{code}
-bash-4.2$ kinit -kt hadoopqa/keytabs/hdfs.headless.keytab hdfs
-bash-4.2$ hdfs dfs -ls o3fs://bucket1.volume1/
19/10/02 19:37:34 INFO ipc.Client: Retrying connect to server:
0.0.0.0/0.0.0.0:9862. Already tried 0 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
19/10/02 19:37:35 INFO ipc.Client: Retrying connect to server:
0.0.0.0/0.0.0.0:9862. Already tried 1 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
19/10/02 19:37:36 INFO ipc.Client: Retrying connect to server:
0.0.0.0/0.0.0.0:9862. Already tried 2 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
^C
{code}
It does not work without host port information as seen above.
Please see after specifying the info it works fine
{code}
-bash-4.2hdfs dfs -ls
o3fs://bucket1.volume1.xxx-xjhgyv-4.xxx-xjhgyv.root.xxx.site:9862/
-bash-4.2$
{code}
> ozonefs paths need host and port information for non HA environment
> ---
>
> Key: HDDS-2229
> URL: https://issues.apache.org/jira/browse/HDDS-2229
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Namit Maheshwari
>Priority: Major
>
>
> For non HA environment ozonefs path need to have host and port info, like
> below:
> o3fs://bucket.volume.om-host:port/key
> Whereas, for HA environments the path will change to use nameservice like
> below:
> o3fs://bucket.volume.ns1/key
> This will create ambiguity. User experience should be the same irrespective
> of the usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-2229) ozonefs paths need host and port information for non HA environment
[ https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942481#comment-16942481 ] Siyao Meng commented on HDDS-2229: -- In non-HA environment, we can omit the port number. In this case, the port number configured in ozone-site.xml will be used. (This is the second case mentioned in [~bharat]'s comment.) Service ID doesn't take a port number because it wouldn't make sense to use one. Such behavior is the same as in HDFS. > ozonefs paths need host and port information for non HA environment > --- > > Key: HDDS-2229 > URL: https://issues.apache.org/jira/browse/HDDS-2229 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Namit Maheshwari >Priority: Major > > > For non HA environment ozonefs path need to have host and port info, like > below: > o3fs://bucket.volume.om-host:port/key > Whereas, for HA environments the path will change to use nameservice like > below: > o3fs://bucket.volume.ns1/key > This will create ambiguity. User experience should be the same irrespective > of the usage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-2229) ozonefs paths need host and port information for non HA environment
[ https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942414#comment-16942414 ] Siyao Meng commented on HDDS-2229: -- Hi [~nmaheshwari], I am able to use the path o3fs://bucket.volume/ (without port or hostname) in the ozone (non-HA) docker-compose cluster. Could you elaborate the specific case where you hit an error? Thanks. > ozonefs paths need host and port information for non HA environment > --- > > Key: HDDS-2229 > URL: https://issues.apache.org/jira/browse/HDDS-2229 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Namit Maheshwari >Priority: Major > > > For non HA environment ozonefs path need to have host and port info, like > below: > o3fs://bucket.volume.om-host:port/key > Whereas, for HA environments the path will change to use nameservice like > below: > o3fs://bucket.volume.ns1/key > This will create ambiguity. User experience should be the same irrespective > of the usage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-2229) ozonefs paths need host and port information for non HA environment
[ https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942410#comment-16942410 ] Bharat Viswanadham commented on HDDS-2229: -- *In non-HA, we support 3 kinds of urls.* o3fs://bucket.volume -> Get hostname and port from config o3fs://bucket.volume.host -> Get port from config o3fs://bucket.volume.host:port *For HA:* o3fs://bucket.volume.<> So, is the purpose of this Jira is to not to support other formats in non-HA? > ozonefs paths need host and port information for non HA environment > --- > > Key: HDDS-2229 > URL: https://issues.apache.org/jira/browse/HDDS-2229 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Namit Maheshwari >Priority: Major > > > For non HA environment ozonefs path need to have host and port info, like > below: > o3fs://bucket.volume.om-host:port/key > Whereas, for HA environments the path will change to use nameservice like > below: > o3fs://bucket.volume.ns1/key > This will create ambiguity. User experience should be the same irrespective > of the usage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
