hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mukul Kumar Singh (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-13079) Provide a config to start namenode in safemode state upto a certain transaction id
Date Mon, 29 Jan 2018 15:21:00 GMT
Mukul Kumar Singh created HDFS-13079:
----------------------------------------

             Summary: Provide a config to start namenode in safemode state upto a certain
transaction id
                 Key: HDFS-13079
                 URL: https://issues.apache.org/jira/browse/HDFS-13079
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
            Reporter: Mukul Kumar Singh
            Assignee: Mukul Kumar Singh


While working on some customer cases it necessary to rollback the Namenode back to a certain
transaction id. This is especially needed when the user issues a {{rm -Rf -skipTrash}}. 

Rolling back to a transaction id helps in taking a peek at the filesystem at a particular
instant. This jira proposes to provide a configuration variable using which the namenode can
be started upto a certain transaction id. The filesystem will be in a readonly safemode which
cannot be overridden manually. It will only be overridden by removing the config value from
the config file.

Please note that in case a checkpoint has already happened and the requested transaction id
has been subsumed in an FSImage, then the namenode will be started with the next nearest transaction
id. Further FSImage files and edits will be ignored.

If the checkpoint hasn't happen then the namenode will be started with the exact transaction
id.



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

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


Mime
View raw message