[
https://issues.apache.org/jira/browse/HDFS-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766127#comment-15766127
]
Uma Maheswara Rao G commented on HDFS-11150:
--------------------------------------------
{quote}
I've tried that before. There is an issue here if we only mark the directory.
When recovering from FsImage, the InodeMap isn't built up, so we don't know the
sub-inode of a given inode, in the end, We cannot add these inodes to movement
queue in FSDirectory#addToInodeMap, any thoughts?
{quote}
I got what you are saying. Ok for simplicity we can add for all Inodes now. For
this to handle 100%, we may need intermittent processing, like first we should
add them to some intermittentList while loading fsImage, once fully loaded and
when starting active services, we should process that list and do required
stuff. But it would add some additional complexity may be. Let's do with all
file inodes now and we can revisit later if it is really creating issues. How
about you raise a JIRA for it and think to optimize separately?
> [SPS]: Provide persistence when satisfying storage policy.
> ----------------------------------------------------------
>
> Key: HDFS-11150
> URL: https://issues.apache.org/jira/browse/HDFS-11150
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Reporter: Yuanbo Liu
> Assignee: Yuanbo Liu
> Attachments: HDFS-11150-HDFS-10285.001.patch,
> HDFS-11150-HDFS-10285.002.patch, editsStored, editsStored.xml
>
>
> Provide persistence for SPS in case that Hadoop cluster crashes by accident.
> Basically we need to change EditLog and FsImage here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
