[HDFS-7503] Namenode restart after large deletions can cause slow processReport (due to logging) - ASF JIRA

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.2.1, 2.6.0
Fix Version/s: 1.3.0, 2.6.1, 3.0.0-alpha1
Component/s: namenode
Labels:
- 2.6.1-candidate

Target Version/s:

1.3.0, 2.7.0
Hadoop Flags:

Reviewed

Description

If a large directory is deleted and namenode is immediately restarted, there are a lot of blocks that do not belong to any file. This results in a log:

2014-11-08 03:11:45,584 INFO BlockStateChange (BlockManager.java:processReport(1901)) - BLOCK* processReport: blk_1074250282_509532 on 172.31.44.17:1019 size 6 does not belong to any file.

This log is printed within FSNamsystem lock. This can cause namenode to take long time in coming out of safemode.

One solution is to downgrade the logging level.