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

ReplicationMonitor thread goes away

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.12.3
    • 0.14.0
    • None
    • None

    Description

      Saw many over/under replicated blocks in fsck output.

      .out file showed

      Exception in thread "org.apache.hadoop.dfs.FSNamesystem$ReplicationMonitor@2785982c" java.lang.IllegalArgumentException: Unexpected non-existing data node: /99.9.99.0/99.9.99.42:99999
      at org.apache.hadoop.net.NetworkTopology.checkArgument(NetworkTopology.java:379)
      at org.apache.hadoop.net.NetworkTopology.isOnSameRack(NetworkTopology.java:424)
      at org.apache.hadoop.dfs.FSNamesystem$ReplicationTargetChooser.chooseTarget(FSNamesystem.java:2853)
      at org.apache.hadoop.dfs.FSNamesystem$ReplicationTargetChooser.chooseTarget(FSNamesystem.java:2816)
      at org.apache.hadoop.dfs.FSNamesystem.pendingTransfers(FSNamesystem.java:2658)
      at org.apache.hadoop.dfs.FSNamesystem.computeDatanodeWork(FSNamesystem.java:1774)
      at org.apache.hadoop.dfs.FSNamesystem$ReplicationMonitor.run(FSNamesystem.java:1723)
      at java.lang.Thread.run(Thread.java:619)

      (same as HADOOP-1232)

      And, jstack showed no ReplicationMonitor thread.

      Attachments

        1. namenodeRestart2.patch
          2 kB
          Dhruba Borthakur

        Issue Links

          Activity

            People

              dhruba Dhruba Borthakur
              knoguchi Koji Noguchi
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: