You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2009/05/06 20:40:30 UTC
[jira] Assigned: (HADOOP-5777) ResolutionMonitor dies on an
exception
[ https://issues.apache.org/jira/browse/HADOOP-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan reassigned HADOOP-5777:
-----------------------------------
Assignee: Jakob Homan
> ResolutionMonitor 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.0
> Reporter: Hairong Kuang
> Assignee: Jakob Homan
>
> 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 ResolutionMonitor thread died 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.