Jinglun created HDFS-14631:
------------------------------
Summary: The DirectoryScanner doesn't fix the wrongly placed
replica.
Key: HDFS-14631
URL: https://issues.apache.org/jira/browse/HDFS-14631
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jinglun
Assignee: Jinglun
When DirectoryScanner scans block files, if the block refers to the block file
does not exist the DirectoryScanner will update the block based on the replica
file found on the disk. See FsDatasetImpl#checkAndUpdate.
{code:java}
/*
* Block exists in volumeMap and the block file exists on the disk
*/
// Compare block files
if (memBlockInfo.blockDataExists()) {
...
} else {
// Block refers to a block file that does not exist.
// Update the block with the file found on the disk. Since the block
// file and metadata file are found as a pair on the disk, update
// the block based on the metadata file found on the disk
LOG.warn("Block file in replica "
+ memBlockInfo.getBlockURI()
+ " does not exist. Updating it to the file found during scan "
+ diskFile.getAbsolutePath());
memBlockInfo.updateWithReplica(
StorageLocation.parse(diskFile.toString()));
LOG.warn("Updating generation stamp for block " + blockId
+ " from " + memBlockInfo.getGenerationStamp() + " to " + diskGS);
memBlockInfo.setGenerationStamp(diskGS);
}
{code}
But the DirectoryScanner doesn't really fix it because in
LocalReplica#parseBaseDir() the 'subdir' are ignored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
