You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/01/03 11:48:15 UTC
[jira] [Commented] (MAPREDUCE-4279) getClusterStatus() fails with
null pointer exception when running jobs in local mode
[ https://issues.apache.org/jira/browse/MAPREDUCE-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542849#comment-13542849 ]
Jarek Jarcec Cecho commented on MAPREDUCE-4279:
-----------------------------------------------
I've recently detected this issue as well. Would it be possible to fix it?
> getClusterStatus() fails with null pointer exception when running jobs in local mode
> ------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4279
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4279
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.23.1, 2.0.0-alpha, 3.0.0
> Reporter: Rahul Jain
> Assignee: Devaraj K
> Attachments: MAPREDUCE-4279.patch
>
>
> While migrating code from 0.20.2 hadoop codebase to 0.23.1 we encountered this issue for jobs run in local mode of execution:
> {code}
> java.lang.NullPointerException
> at org.apache.hadoop.mapred.JobClient.arrayToStringList(JobClient.java:783)
> at org.apache.hadoop.mapred.JobClient.access$600(JobClient.java:138)
> at org.apache.hadoop.mapred.JobClient$4.run(JobClient.java:815)
> at org.apache.hadoop.mapred.JobClient$4.run(JobClient.java:812)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1177)
> at org.apache.hadoop.mapred.JobClient.getClusterStatus(JobClient.java:812)
> {code}
> We are using cloudera distribution CDH4b2 for testing, however the underlying code is 0.23.1 and I could see no difference in this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira