[
https://issues.apache.org/jira/browse/HDFS-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036396#comment-13036396
]
Todd Lipcon commented on HDFS-1505:
-----------------------------------
Hey Matt. You're pretty close.
bq. And you're referring to the resulting fact that one could take an image
ending with txn 100, jump into the middle of a log file that went from txn 50
to 170
In theory, yes. In the current implementation, images are only saved at
boundaries of edit log segments. So if you have an image with txn 100, then
you'll have some edit log file which starts at 101, so the "jump into the
middle" part isn't necessary.
bq. Although it doesn't hurt to also clear the edits logs, once you have
multiple copies of the fsimage. Does your log-rolling logic automatically
delete log chunk files older than available fsimage files?
It's not implemented yet, but the idea is that a separate background thread
would be responsible for handling management of old files based on various
policies (eg remove old ones, or perhaps archive to some other location)
So, sounds like we're in agreement. Thanks.
> saveNamespace appears to succeed even if all directories fail to save
> ---------------------------------------------------------------------
>
> Key: HDFS-1505
> URL: https://issues.apache.org/jira/browse/HDFS-1505
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Todd Lipcon
> Assignee: Aaron T. Myers
> Priority: Blocker
> Fix For: 0.22.0
>
> Attachments: hdfs-1505-1-test.txt, hdfs-1505-22.0.patch,
> hdfs-1505-22.1.patch, hdfs-1505-22.2.patch, hdfs-1505-test.txt,
> hdfs-1505-trunk.0.patch, hdfs-1505-trunk.1.patch, hdfs-1505-trunk.2.patch,
> hdfs-1505-trunk.3.patch
>
>
> After HDFS-1071, saveNamespace now appears to "succeed" even if all of the
> individual directories failed to save.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
