Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-11672

Fix some misleading log messages related to EC block groups

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 3.0.0-alpha1
    • None
    • erasure-coding

    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
      

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            manojg Manoj Govindassamy
            andrew.wang Andrew Wang

            Dates

              Created:
              Updated:

              Slack

                Issue deployment