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

Hudson commented on HDDS-1457:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16461 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16461/])
HDDS-1457. Sequence of configuring Ozone File System instruction needs (elek: 
rev e95c055d910c13ab0c6e0ff157b59d2b9cd936e6)
* (edit) hadoop-hdds/docs/content/OzoneFS.md
* (edit) hadoop-hdds/docs/content/BuildingSources.md
* (edit) hadoop-hdds/docs/content/RunningWithHDFS.md


> Sequence of configuring Ozone File System instruction needs some work
> ---------------------------------------------------------------------
>
>                 Key: HDDS-1457
>                 URL: https://issues.apache.org/jira/browse/HDDS-1457
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Major
>             Fix For: 0.4.0
>
>         Attachments: HDDS-1457.001.patch
>
>
> Novice user may start trying out ozone fs command after completing Starting 
> an Ozone Cluster instructions.  This is because the next section "Running 
> concurrently with HDFS", "Building from source" are loosely coupled topic, 
> but not important to the task of setting up a ozone cluster. By following the 
> current flow of instruction, cluster does not work at this point.  
> The recommendation is to move instruction of Ozone File System to 
> Configuration section.  Client Configuration as a second step to ensure 
> core-site.xml is configured correctly.  After starting an Ozone Cluster, 
> follow by volume and bucket creation command.  This will make the setup flow 
> smoother, and better initial user experience.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to