Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.1.0
    • Fix Version/s: 0.12.0
    • Component/s: None
    • Labels:
      None

      Description

      When the block is under-replicated the namenode places it into
      FSNamesystem.neededReplications list.
      When a datanode D1 sends getBlockwork() request to the namenode, the namenode
      selects another node D2 (which it thinks is up and running) where the new replica of the
      under-replicated block will be stored.
      Then namenode removes the block from the neededReplications list and places it to
      the pendingReplications list, and then asks D1 to replicate the block to D2.
      If D2 is in fact down, then replication will fail and will never be retried later, because
      the block is not in the neededReplications list, but rather in the pendingReplications list,
      which namenode never checks.

        Issue Links

          Activity

          Hide
          Doug Cutting added a comment -

          This was fixed as a part of HADOOP-940.

          Show
          Doug Cutting added a comment - This was fixed as a part of HADOOP-940 .

            People

            • Assignee:
              Konstantin Shvachko
              Reporter:
              Konstantin Shvachko
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development