You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "J.Andreina (JIRA)" <ji...@apache.org> on 2015/04/26 11:45:38 UTC

[jira] [Updated] (HDFS-8226) Non-HA rollback compatibility broken

     [ https://issues.apache.org/jira/browse/HDFS-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.Andreina updated HDFS-8226:
-----------------------------
    Attachment: HDFS-8226.1.patch

I have updated an initial patch . This has document updation for the steps to perform Non-HA rollback ( which is incompatible with older releases). 

Please provide your feedback on this approach .


> Non-HA rollback compatibility broken
> ------------------------------------
>
>                 Key: HDFS-8226
>                 URL: https://issues.apache.org/jira/browse/HDFS-8226
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: J.Andreina
>            Assignee: J.Andreina
>            Priority: Blocker
>         Attachments: HDFS-8226.1.patch
>
>
> In HA  while performing rollback , we use “hdfs namenode –rollback” which would prompt user for confirmation.  ( Implemented as part of HDFS-5138)
> For Non-HA , as per doc if we perform rollback using “start-dfs.sh –rollback” , then namenode startup hangs ( As it tries to start namenode in daemon mode , hence will not be able to prompt user for confirmation )



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)