hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6240) Hadoop client displays confusing error message
Date Tue, 30 Jun 2015 23:03:05 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609224#comment-14609224
] 

Chris Douglas commented on MAPREDUCE-6240:
------------------------------------------

Minor (not blocking for commit):
- This could just add the {{IOException}} to the list instead of throw/catch
- The message doesn't need to append {{t}}:
{noformat}
+            ioExceptions.add(new IOException("Failed to initialize protocol: "
+                + t, t));
{noformat}
- Should this continue to catch only {{Exception}}, instead of {{Throwable}}? 
- If the cause of the exception is an {{IOException}}, this discards the caught exception?
Is this a special/common case?

It's a little odd to wrap all of this as an {{IOException}}, but I don't think it's worth
adding another composite type.

> Hadoop client displays confusing error message
> ----------------------------------------------
>
>                 Key: MAPREDUCE-6240
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6240
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.7.0
>            Reporter: Mohammad Kamrul Islam
>            Assignee: Gera Shegalov
>         Attachments: MAPREDUCE-6240-gera.001.patch, MAPREDUCE-6240-gera.001.patch, MAPREDUCE-6240-gera.002.patch,
MAPREDUCE-6240.003.patch, MAPREDUCE-6240.1.patch
>
>
> Hadoop client often throws exception  with "java.io.IOException: Cannot initialize Cluster.
Please check your configuration for mapreduce.framework.name and the correspond server addresses".
> This is a misleading and generic message for any cluster initialization problem. It takes
a lot of debugging hours to identify the root cause. The correct error message could resolve
this problem quickly.
> In one such instance, Oozie log showed the following exception  while the root cause
was CNF  that Hadoop client didn't return in the exception.
> {noformat}
>  JA009: Cannot initialize Cluster. Please check your configuration for mapreduce.framework.name
and the correspond server addresses.
>         at org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:412)
>         at org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:392)
>         at org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:979)
>         at org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1134)
>         at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:228)
>         at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:63)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:281)
>         at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:323)
>         at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:252)
>         at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:174)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:744)
> Caused by: java.io.IOException: Cannot initialize Cluster. Please check your configuration
for mapreduce.framework.name and the correspond server addresses.
>         at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:120)
>         at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:82)
>         at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:75)
>         at org.apache.hadoop.mapred.JobClient.init(JobClient.java:470)
>         at org.apache.hadoop.mapred.JobClient.<init>(JobClient.java:449)
>         at org.apache.oozie.service.HadoopAccessorService$1.run(HadoopAccessorService.java:372)
>         at org.apache.oozie.service.HadoopAccessorService$1.run(HadoopAccessorService.java:370)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at javax.security.auth.Subject.doAs(Subject.java:415)
>         at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
>         at org.apache.oozie.service.HadoopAccessorService.createJobClient(HadoopAccessorService.java:379)
>         at org.apache.oozie.action.hadoop.JavaActionExecutor.createJobClient(JavaActionExecutor.java:1185)
>         at org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:927)
>  ... 10 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message