[jira] [Comment Edited] (HDDS-2229) ozonefs paths need host and port information for non HA environment

2019-10-02 Thread Siyao Meng (Jira)


[ 
https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943175#comment-16943175
 ] 

Siyao Meng edited comment on HDDS-2229 at 10/2/19 9:30 PM:
---

[~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 number are 
omitted. This is not a bug on the code side.
Anyway, thanks for filing this. Closing this jira now.


was (Author: smeng):
[~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] [Comment Edited] (HDDS-2229) ozonefs paths need host and port information for non HA environment

2019-10-01 Thread Bharat Viswanadham (Jira)


[ 
https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942410#comment-16942410
 ] 

Bharat Viswanadham edited comment on HDDS-2229 at 10/2/19 1:00 AM:
---

*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, this Jira is opened for which issue, I have not clearly understood.


was (Author: bharatviswa):
*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