You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2013/06/06 23:00:20 UTC
[jira] [Resolved] (HDFS-4867) metaSave NPEs when there are invalid
blocks in repl queue.
[ https://issues.apache.org/jira/browse/HDFS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko resolved HDFS-4867.
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.5-alpha)
(was: 3.0.0)
0.23.9
2.1.0-beta
Release Note: I just committed this. Thank you Plamen and Ravi.
Hadoop Flags: Reviewed
> 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.7, 2.0.4-alpha, 0.23.8
> Reporter: Kihwal Lee
> Assignee: Plamen Jeliazkov
> Fix For: 2.1.0-beta, 0.23.9
>
> Attachments: HDFS-4867.branch-0.23.patch, HDFS-4867.branch-0.23.patch, HDFS-4867.branch-0.23.patch, HDFS-4867.branch-0.23.patch, HDFS-4867.branch-2.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, 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