Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 26 Sep 2013 19:35:05 +0000 (UTC)
From: "Vrushali C (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12667936.1378851533720.25951.1380224105094@arcas>
In-Reply-To: <JIRA.12667936.1378851533720@arcas>
References: <JIRA.12667936.1378851533720@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5502) History link in resource manager
 is broken for KILLED jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vrushali C updated MAPREDUCE-5502:
----------------------------------

    Status: Patch Available  (was: Open)
    
> History link in resource manager is broken for KILLED jobs
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-5502
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5502
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.5-alpha
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>              Labels: ui
>         Attachments: patch_5502_2.txt, patch_5502_3.txt, patch_5502.txt
>
>
> History link in resource manager is broken for KILLED jobs.
> Seems to happen with jobs with State 'KILLED' and FinalStatus 'KILLED'. If the State is 'FINISHED' and FinalStatus is 'KILLED', then the "History" link is fine.
> It isn't easy to reproduce the problem since the time at which the app is killed determines the state it ends up in, which is hard to guess. these particular jobs seem to get a Diagnostics message of "Application killed by user." where as the other killed jobs get " Kill Job received from client job_1378766187901_0002
> Job received Kill while in RUNNING state. "

--
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