[HDFS-11672] Fix some misleading log messages related to EC block groups

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.0.0-alpha1
• Component/s: erasure-coding
• Labels: newbie
• Target Version/s: 3.5.0
• Assignee: Manoj Govindassamy
• Reporter: Andrew Wang
• Created: 19/Apr/17 00:26
• Updated: 04/Jan/24 07:24

Description

I turned the NameNode's BlockStateChange and hdfs.StateChange logs up to debug, noticed some out of date log messages like the following:

2017-04-18 17:19:50,639 [IPC Server handler 4 on 45133] DEBUG hdfs.StateChange (FSDirWriteFileOp.java:addBlock(507)) - DIR* FSDirectory.addBlock: /test2RecoveryTasksForSameBlockGroup with blk_-9223372036854775792_1001 block is added to the in-memory file system

2017-04-18 17:19:50,836 [Block report processor] DEBUG BlockStateChange (LowRedundancyBlocks.java:update(353)) - BLOCK* NameSystem.LowRedundancyBlock.update: blk_-9223372036854775792_1001 has only 8 replicas and needs 9 replicas so is added to neededReconstructions at priority level 2

2017-04-18 17:19:51,235 [IPC Server handler 4 on 45133] DEBUG hdfs.StateChange (FSNamesystem.java:closeFile(3740)) - closeFile: /test2RecoveryTasksForSameBlockGroup with 1 blocks is persisted to the file system