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

Hudson commented on HDDS-490:
-----------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15791 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15791/])
HDDS-684. Fix HDDS-4 branch after HDDS-490 and HADOOP-15832. Contributed (xyao: 
rev 61e85d7cd1a69686c0793fadd105d7675dd373e1)
* (edit) hadoop-ozone/dist/dev-support/bin/dist-layout-stitching
* (edit) hadoop-ozone/dist/src/main/compose/ozonesecure/docker-config
* (edit) 
hadoop-ozone/dist/src/main/compose/ozonesecure/docker-image/runner/scripts/starter.sh
* (edit) 
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java


> Improve om and scm start up options 
> ------------------------------------
>
>                 Key: HDDS-490
>                 URL: https://issues.apache.org/jira/browse/HDDS-490
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Namit Maheshwari
>            Assignee: Namit Maheshwari
>            Priority: Major
>              Labels: alpha2, incompatible
>             Fix For: 0.3.0, 0.4.0
>
>         Attachments: HDDS-490.001.patch, HDDS-490.002.patch
>
>
> I propose the following changes:
>  # Rename _createObjectStore_ to _init_
>  # Use double-dash for all long options (Unix convention)
>  # Format existing object store should be a no-op. If a user runs:
> {code:java}
> ozone om --init{code}
> And OM is already initialized, it should give a warning message and exit the 
> process with success.



--
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