[ 
https://issues.apache.org/jira/browse/HDDS-1891?focusedWorklogId=291684&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291684
 ]

ASF GitHub Bot logged work on HDDS-1891:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Aug/19 00:51
            Start Date: 09/Aug/19 00:51
    Worklog Time Spent: 10m 
      Work Description: smengcl commented on issue #1218: HDDS-1891. Ozone fs 
shell command should work with default port when port number is not specified
URL: https://github.com/apache/hadoop/pull/1218#issuecomment-519737497
 
 
   > > One more comment, I think we should make a similar change in 
BasicOzoneFileSystem.java.
   > > See, can we have a some utility method, which can be used across 2 
classes.
   > 
   > OzoneFileSystem extends BasicOzoneFileSystem, so this has been taken care. 
Just test it out locally.
   
   While I'm testing it in a docker-compose cluster, it seems that the change 
of `authority` 
[here](https://github.com/apache/hadoop/pull/1218/commits/ab93f4bc3fd8d2acf31dac5bbf79c49546eccacd#diff-e48c4ce6b86d4a33c3f38ba8d6d06ea3R129)
 might have broken something. It throws error:
   ```
   bash-4.2$ ozone fs -ls o3fs://bucket.volume.om/
   -ls: Wrong FS: o3fs://bucket.volume.om/, expected: 
o3fs://bucket.volume.om:9862
   ...
   ```
   
   After I commented out this line, compiled and re-tested, it works again:
   ```
   bash-4.2$ ozone fs -ls o3fs://bucket.volume.om/
   Found 1 items
   -rw-rw-rw-   1 hadoop hadoop       1485 1970-01-01 00:46 
o3fs://bucket.volume.om/README.txt
   ```
   
   FYI my test prep steps:
   ```bash
   mvn clean install -f pom.ozone.xml -DskipTests=true -Dmaven.javadoc.skip=true
   cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone
   docker-compose up -d --scale datanode=3
   docker-compose exec om /bin/bash
   ozone sh volume create /volume
   ozone sh bucket create /volume/bucket
   vi /etc/hadoop/core-site.xml
   # Add fs.o3fs.impl and fs.defaultFS config and save
   # Ref: https://hadoop.apache.org/ozone/docs/0.4.0-alpha/ozonefs.html
   ozone fs -put README.txt o3fs:///
   ozone fs -ls /
   ```
   
   Investigating.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 291684)
    Time Spent: 2h 10m  (was: 2h)

> Ozone fs shell command should work with default port when port number is not 
> specified
> --------------------------------------------------------------------------------------
>
>                 Key: HDDS-1891
>                 URL: https://issues.apache.org/jira/browse/HDDS-1891
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Siyao Meng
>            Assignee: Siyao Meng
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> {code:bash|title=Without port number -> Error}
> $ ozone fs -ls o3fs://bucket.volume.localhost/
> -ls: Ozone file system url should be either one of the two forms: 
> o3fs://bucket.volume/key  OR o3fs://bucket.volume.om-host.example.com:5678/key
> ...
> {code}
> {code:bash|title=With port number -> Success}
> $ ozone fs -ls o3fs://bucket.volume.localhost:9862/
> Found 1 items
> -rw-rw-rw-   1 hadoop hadoop       1485 2019-08-01 21:14 
> o3fs://bucket.volume.localhost:9862/README.txt
> {code}
> We expect the first command to attempt port 9862 by default.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to