[
https://issues.apache.org/jira/browse/HDFS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HDFS-4867:
--------------------------------------
Status: Open (was: Patch Available)
Checked the patches. They still fail, sorry. I think the problem is that
orphaned blocks are still present and reported in metasave. That is if you run
testMetaSaveWithOrphanedBlocks() first then testMetaSave() they fail, because
the reports are different from what is expected.
So I propose to remove testMetaSaveWithOrphanedBlocks() for this patch. Because
HDFS-4878 will break it right away. So why don't we include this test to
HDFS-4878 instead. Should be modified for the output there. The order of
running test cases after that shouldn't matter because there will be no
orphaned blocks.
> metaSave NPEs when there are invalid blocks in repl queue.
> ----------------------------------------------------------
>
> Key: HDFS-4867
> URL: https://issues.apache.org/jira/browse/HDFS-4867
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.23.8, 2.0.4-alpha, 0.23.7
> Reporter: Kihwal Lee
> Assignee: Plamen Jeliazkov
> Fix For: 3.0.0, 2.0.5-alpha
>
> Attachments: HDFS-4867.branch-0.23.patch,
> HDFS-4867.branch-0.23.patch, HDFS-4867.branch2.patch,
> HDFS-4867.branch2.patch, HDFS-4867.branch2.patch, HDFS-4867.trunk.patch,
> HDFS-4867.trunk.patch, HDFS-4867.trunk.patch, testMetaSave.log
>
>
> Since metaSave cannot get the inode holding a orphaned/invalid block, it NPEs
> and stops generating further report. Normally ReplicationMonitor removes them
> quickly, but if the queue is huge, it takes very long time. Also in safe
> mode, they stay.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
