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 "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2014/01/16 02:48:21 UTC

[jira] [Resolved] (MAPREDUCE-5628) Tracking ids only for HDFS tokens should be included in jobconf

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla resolved MAPREDUCE-5628.
-----------------------------------------

    Resolution: Not A Problem

My bad. Token#getTrackingId() never returns null. 

> Tracking ids only for HDFS tokens should be included in jobconf
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-5628
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5628
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: job submission
>    Affects Versions: 2.2.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Critical
>
> MAPREDUCE-5379 adds the ability to track HDFS accesses of an MR job by adding the tracking-ids from all the tokens to the jobconf. However, only HDFS delegation tokens have a tracking-id. Trying to fetch tracking-ids from other tokens can lead to an NPE.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)