[
https://issues.apache.org/jira/browse/HDFS-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299128#comment-14299128
]
Tsz Wo Nicholas Sze commented on HDFS-7648:
-------------------------------------------
> It's not the goal of DirectoryScanner to fix anything. ...
The original design of DirectoryScanner is to reconciles the differences
between the block information maintained in memory and the actual blocks stored
in disks. So it does fix the in-memory data structure.
> What would be the suggested way to fix these unmatched blocks. Also, if it is
> not fixed then this warning message will be printed repeatedly during the
> directory scanning interval.
Yet more questions if the blocks are not fixed: should the block report include
those blocks? How to access those blocks? How and when to fix those blocks?
It seems fixing the blocks is better. Of course, we still log an error message
for those blocks.
> Verify the datanode directory layout
> ------------------------------------
>
> Key: HDFS-7648
> URL: https://issues.apache.org/jira/browse/HDFS-7648
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Rakesh R
>
> HDFS-6482 changed datanode layout to use block ID to determine the directory
> to store the block. We should have some mechanism to verify it. Either
> DirectoryScanner or block report generation could do the check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
