[HDFS-4080] Add a separate logger for block state change logs to enable turning off those logs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha, 3.0.0-alpha1
• Fix Version/s: 2.0.3-alpha, 0.23.5
• Component/s: namenode
• Target Version/s: 2.0.3-alpha, 0.23.5
• Hadoop Flags: Incompatible change, Reviewed
• Release Note: Add a separate logger "BlockStateChange" for block state change logs.
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 19/Oct/12 01:34
• Updated: 12/May/16 18:14
• Resolved: 09/Nov/12 18:34

Description

Although the block-level logging in namenode is useful for debugging, it can add a significant overhead to busy hdfs clusters since they are done while the namespace write lock is held. One example is shown in HDFS-4075. In this example, the write lock was held for 5 minutes while logging 11 million log messages for 5.5 million block invalidation events.

It will be useful if we have an option to disable these block-level log messages and keep other state change messages going. If others feel that they can turned into DEBUG (with addition of isDebugEnabled() checks), that may also work too, but there might be people depending on the messages.

Issue Links

• is related to: HDFS-7425 NameNode block deletion logging uses incorrect appender.
• relates to: HDFS-4075 Reduce recommissioning overhead