[
https://issues.apache.org/jira/browse/HADOOP-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706269#action_12706269
]
Hairong Kuang commented on HADOOP-5777:
---------------------------------------
ResolutionMonitor was removed by HADOOP-3620 in 0.19. So it may not worth
fixing the dead thread problem. But it is still worth figuring out what caused
the StringIndexOutofBoundsException.
> ResolutionMointor dies on an exception
> --------------------------------------
>
> Key: HADOOP-5777
> URL: https://issues.apache.org/jira/browse/HADOOP-5777
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.3
> Reporter: Hairong Kuang
>
> One of our dfs clusters went into an unhealthy state, where many datanodes
> have non-zero bytes but no rack information. It turned out the
> ResolutionMoinitor thread dies on an exception. Here is the stack trace of
> the exception that caused the problem:
> ERROR org.apache.hadoop.fs.FSNamesystem:
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1938)
> at java.lang.String.substring(String.java:1905)
> at
> org.apache.hadoop.net.NetworkTopology$InnerNode.getNextAncestorName(NetworkTopology.java:119)
> at
> org.apache.hadoop.net.NetworkTopology$InnerNode.add(NetworkTopology.java:153)
> at org.apache.hadoop.net.NetworkTopology.add(NetworkTopology.java:329)
> at
> org.apache.hadoop.dfs.FSNamesystem$ResolutionMonitor.run(FSNamesystem.java:1885)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
