[HADOOP-1486] ReplicationMonitor thread goes away

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.12.3
• Fix Version/s: 0.14.0
• Assignee: Dhruba Borthakur
• Reporter: Koji Noguchi
• Created: 12/Jun/07 16:44
• Updated: 08/Jul/09 16:42
• Resolved: 11/Jul/07 21:29

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.

Issue Links

• relates to: HADOOP-1605 Automatic namenode restart when it encounters an error situation