Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <2055786649.1253184837817.JavaMail.jira@brutus>
Date: Thu, 17 Sep 2009 03:53:57 -0700 (PDT)
From: "Jothi Padmanabhan (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-995) JobHistory should handle cases
 where task completion events are generated after job completion event
In-Reply-To: <897157612.1253182797495.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jothi Padmanabhan updated MAPREDUCE-995:
----------------------------------------

    Status: Patch Available  (was: Open)

> JobHistory should handle cases where task completion events are generated after job completion event
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-995
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-995
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Jothi Padmanabhan
>            Assignee: Jothi Padmanabhan
>         Attachments: mapred-995.patch
>
>
> It is apparently possible, in certain circumstances (failed job, for example), for the job history to get task completion events after the job completion event. This currently causes NPE in job history.
> Thanks Hong for identifying this issue

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.