Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-5780

Fix slightly confusing log from "-metaSave" on NameNode

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.20.0
    • Fix Version/s: 0.21.0
    • Component/s: None
    • Labels:
      None

      Description

      After HADOOP-4103, "-metaSave" on NameNode prints "MISSING" in the line for a block that does not have any good replicas left.

      e.g. :

      Metasave: Blocks waiting for replication: 1
      blk_6735500019364591152_0 (replicas: l: 0 d: 0 c: 2 e: 0 MISSING) 74.6.132.200:50010 :  192.168.0.107:50010 :
      

      "0 MISSING" in the log might imply to the user that there is no missing block, though it implies "e(xcess replicas) : 0".

      We should fix that. Also as part of this I would like to indicate which datanodes are decommissioned or contain the corrupt replicas.

        Attachments

        1. HADOOP-5780.hadoop-0.20.patch
          2 kB
          Jitendra Nath Pandey
        2. HADOOP-5780.patch
          3 kB
          Raghu Angadi
        3. HADOOP-5780.patch
          3 kB
          Raghu Angadi
        4. HADOOP-5780.patch
          2 kB
          Raghu Angadi

          Activity

            People

            • Assignee:
              rangadi Raghu Angadi
              Reporter:
              rangadi Raghu Angadi
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: