[ https://issues.apache.org/jira/browse/HDDS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.<<nameservice>> 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.<<nameservice>> 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