AnsweredAssumed Answered

StringIndexOutOfBoundsException

Question asked by impermisha on Jun 22, 2012
Latest reply on Jul 15, 2012 by impermisha
We are seeing errors with the following stack trace.  Is it possible the cache of name look up is corrupt on a node?  If so where would I go look to blow it away? any other ideas?  note this job worked fine on an older cloudera cluster, it is just on our new cluster using mapr we get this intermitten error

    Failure Info:Job initialization failed: java.lang.StringIndexOutOfBoundsException: String index  out of range: 0 at java.lang.String.charAt(String.java:686) at org.apache.hadoop.net.NetUtils.normalizeHostName(NetUtils.java:436) at org.apache.hadoop.net.NetUtils.normalizeHostNames(NetUtils.java:459) at org.apache.hadoop.net.CachedDNSToSwitchMapping.resolve(CachedDNSToSwitchMapping.java:42) at org.apache.hadoop.mapred.JobTracker.resolveAndAddToTopology(JobTracker.java:3491) at org.apache.hadoop.mapred.JobInProgress.createCache(JobInProgress.java:618) at org.apache.hadoop.mapred.JobInProgress.initTasks(JobInProgress.java:796) at org.apache.hadoop.mapred.JobTracker.initJob(JobTracker.java:4646) at org.apache.hadoop.mapred.EagerTaskInitializationListener$InitJob.run(EagerTaskInitializationListener.java:79) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

Outcomes