Modifying the Hadoop/hdfs log level

Describe:

If A large directory is deleted and Namenode was immediately restarted, there is a lot of blocks that does 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 no belong to any file.

This log is printed within Fsnamsystem lock. This can cause Namenode to take a long time in coming out of SafeMode.

One solution is to downgrade the logging level.

Solution Solutions

Tail-f/var/log/hadoop/hdfs/hdfs-namenode.log

Http://<namenode:50070>/logLevel

Input "Blockstatechange" and "WARN" and "click" Set Log Level "button

Wait up to mins. It works and performance is fine.

This article is from the "Han Lei" blog, make sure to keep this source http://deararvin.blog.51cto.com/11158301/1742542

Modifying the Hadoop/hdfs log level