You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Eli Collins (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/29 18:38:28 UTC
[jira] [Resolved] (HADOOP-6757) NullPointerException for hadoop
clients launched from streaming tasks
[ https://issues.apache.org/jira/browse/HADOOP-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins resolved HADOOP-6757.
---------------------------------
Resolution: Fixed
I think this is fixed in branch-1, and is not relevant to other releases.
> NullPointerException for hadoop clients launched from streaming tasks
> ---------------------------------------------------------------------
>
> Key: HADOOP-6757
> URL: https://issues.apache.org/jira/browse/HADOOP-6757
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Attachments: BZ-3620565-v1.0.patch, HADOOP-6757-v1.0.patch
>
>
> TaskRunner sets HADOOP_ROOT_LOGGER to info,TLA while launching the child tasks. TLA implicitly assumes that that task-id information will be made available via the 'hadoop.tasklog.taskid' parameter. 'hadoop.tasklog.taskid' is passed to the child task by the TaskRunner via HADOOP_CLIENT_OPTS. When the streaming task launches a hadoop client (say hadoop job -list), the HADOOP_ROOT_LOGGER of the hadoop client is set to 'info,TLA' but hadoop.tasklog.taskid is not set resulting into NPE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira