Hadoop Common
  1. Hadoop Common
  2. HADOOP-4597

Under-replicated blocks are not calculated if the name-node is forced out of safe-mode.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.18.0
    • Fix Version/s: 0.18.3
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Currently during name-node startup under-replicated blocks are not added to the neededReplications queue until the name-node leaves safe mode. This is an optimization since otherwise all blocks will first go into the under-replicated queue and then most of them will be removed from it.
      When the name-node leaves safe-mode automatically it checks all blocks to have a correct number of replicas (processMisReplicatedBlocks()).
      When the name-node leaves safe-mode manually it does not perform the checkup.
      In the latter case all under-replicated blocks remain not replicated forever because there is no alternative mechanism to trigger replications.
      The proposal is to call processMisReplicatedBlocks() any time the name-node leaves safe mode - automatically or manually.
      In addition to solving that problem this could be an alternative mechanism for refreshing neededReplications and excessReplicateMap sets.

      1. NeededRepl-18.patch
        0.5 kB
        Konstantin Shvachko
      2. NeededRepl.patch
        0.6 kB
        Konstantin Shvachko

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development