[
https://issues.apache.org/jira/browse/HDFS-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833361#comment-13833361
]
Jing Zhao commented on HDFS-5568:
---------------------------------
Hmm. My original thought is that since we now do not support nested
snapshottable directories, for a given directory, we only have at most one
snapshottable directory and we should be able to check the corresponding
snapshot paths.
But after more thinking, looks like the challenge here is that the given
directory can be a renamed directory. In that case, it is hard to identify the
correct snapshot paths. So I think the current solution is good and we do not
need to support that case here.
> Support inclusion of snapshot paths in Namenode fsck
> ----------------------------------------------------
>
> Key: HDFS-5568
> URL: https://issues.apache.org/jira/browse/HDFS-5568
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
> Reporter: Vinay
> Assignee: Vinay
> Attachments: HDFS-5568-1.patch, HDFS-5568.patch, HDFS-5568.patch
>
>
> Support Fsck to check the snapshot paths also for inconsistency.
> Currently Fsck supports snapshot paths if path given explicitly refers to a
> snapshot path.
> We have seen safemode problems in our clusters which were due to blocks
> missing which were only present inside snapshots. But "hdfs fsck /" shows
> HEALTHY.
> So supporting snapshot paths also during fsck (may be by default or on
> demand) would be helpful in these cases instead of specifying each and every
> snapshottable directory.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
