[
https://issues.apache.org/jira/browse/HADOOP-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235194#comment-13235194
]
Brandon Li commented on HADOOP-4885:
------------------------------------
bq. since we haven't started the edits.new file yet, something may actually
block??
Filesystem modification can be blocked. This step should be optimized. By
default, the automatic restore is disabled.
bq. It would be better if the resyncing up to the last closed edit log is done
asynchronously.
This could be a way to optimize the operation. Another way is not to copy over
the files but wait for the checkpoint processing to populate the new image and
edit logs. For the second approach the storage directories under restoring
should have a new state (e.g., formatted or restoring) rather than "active".
bq. Ideally any exceptions from dealing with the removed dirs should be ignored.
Agree.
> Try to restore failed replicas of Name Node storage (at checkpoint time)
> ------------------------------------------------------------------------
>
> Key: HADOOP-4885
> URL: https://issues.apache.org/jira/browse/HADOOP-4885
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Fix For: 0.21.0
>
> Attachments: HADOOP-4885-1.patch, HADOOP-4885-3.patch,
> HADOOP-4885-3.patch, HADOOP-4885.branch-1.patch,
> HADOOP-4885.branch-1.patch.2, HADOOP-4885.branch-1.patch.3,
> HADOOP-4885.patch, HADOOP-4885.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
