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

Hudson commented on HDFS-12796:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-12796. SCM should not start if Cluster Version file does not exist. 
(nanda: rev b8297b0846d20ebeed05932c5a950dd826343a07)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/scm/StorageContainerManager.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/ozone/TestStorageContainerManager.java


> SCM should not start if Cluster Version file does not exist
> -----------------------------------------------------------
>
>                 Key: HDFS-12796
>                 URL: https://issues.apache.org/jira/browse/HDFS-12796
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: HDFS-7240
>
>         Attachments: HDFS-12796-HDFS-7240.001.patch, 
> HDFS-12796-HDFS-7240.002.patch, HDFS-12796-HDFS-7240.003.patch
>
>
> We have SCM --init command which persist the cluster Version info in the 
> version file.  If SCM gets 
> started without SCM --init being done even once, it should fail.



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

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