Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.23.7, 2.0.4-alpha, 0.23.8
-
None
-
Reviewed
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
HDFS-3974 dfsadmin -metasave throws NPE when under-replicated blocks are recently deleted
- Open