[
https://issues.apache.org/jira/browse/HDFS-11672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802494#comment-17802494
]
Shilun Fan commented on HDFS-11672:
-----------------------------------
Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a
blocker. Retarget 3.5.0.
> Fix some misleading log messages related to EC block groups
> -----------------------------------------------------------
>
> Key: HDFS-11672
> URL: https://issues.apache.org/jira/browse/HDFS-11672
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: Manoj Govindassamy
> Priority: Minor
> Labels: newbie
>
> I turned the NameNode's BlockStateChange and hdfs.StateChange logs up to
> debug, noticed some out of date log messages like the following:
> {noformat}
> 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
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
