[
https://issues.apache.org/jira/browse/HDFS-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319531#comment-16319531
]
Virajith Jalaparti commented on HDFS-12996:
-------------------------------------------
Thanks for posting the design document [~hanishakoneru]. A few questions -
# In Section 13, Step 5, which component receives the _restore-replica-trash_
command? From my understanding this should be the Namenode. However, in step 5
the Namenode is not running. How is this going to work?
# Have you looked at "undoing" the delete operation? I think this would need to
handle conflicts (for example, /foo/bar was deleted but a new /foo/bar/ is
created) but could avoid having to stop and restart the Namenode.
> DataNode Replica Trash
> ----------------------
>
> Key: HDFS-12996
> URL: https://issues.apache.org/jira/browse/HDFS-12996
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Attachments: DataNode_Replica_Trash_Design_Doc.pdf
>
>
> DataNode Replica Trash will allow administrators to recover from a recent
> delete request that resulted in catastrophic loss of user data. This is
> achieved by placing all invalidated blocks in a replica trash on the datanode
> before completely purging them from the system. The design doc is attached
> here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
