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

fsck is confusing when dfs.namenode.replication.min > 1 && missing replicas && NN restart

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7.0
    • Component/s: namenode
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      If minimum replication is set to 2 or higher and some of those replicas are missing and the namenode restarts, it isn't always obvious that the missing replicas are the reason why the namenode isn't leaving safemode. We should improve the output of fsck and the web UI to make it obvious that the missing blocks are from unmet replicas vs. completely/totally missing.

        Attachments

        1. Screen Shot 2015-02-26 at 10.30.35.png
          85 kB
          Rui Gao
        2. Screen Shot 2015-02-26 at 10.27.46.png
          128 kB
          Rui Gao
        3. HDFS-7537.2.patch
          7 kB
          Rui Gao
        4. HDFS-7537.1.patch
          3 kB
          Rui Gao
        5. dfs-min-2-fsck.png
          12 kB
          Allen Wittenauer
        6. dfs-min-2.png
          27 kB
          Allen Wittenauer

          Issue Links

            Activity

              People

              • Assignee:
                demongaorui Rui Gao
                Reporter:
                aw Allen Wittenauer
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: