hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nanda kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12796) SCM should not start if Cluster Version file does not exist
Date Thu, 09 Nov 2017 16:40:00 GMT

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

Nanda kumar commented on HDFS-12796:

Thanks [~shashikant] for reporting and working on the issue.
The patch looks good to me. One small comment though, instead of using {{try .. cache ..}}
block for asserting the Exception we can use {{org.junit.rules.ExpectedException}}. 

> 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
>             Fix For: HDFS-7240
>         Attachments: HDFS-12796-HDFS-7240.001.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

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

View raw message