Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 28 Jan 2014 00:25:39 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12690162.1390354039550.22726.1390868739771@arcas>
In-Reply-To: <JIRA.12690162.1390354039550@arcas>
References: <JIRA.12690162.1390354039550@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5732) Report proper queue when job
 has been automatically placed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883559#comment-13883559 ] 

Sandy Ryza commented on MAPREDUCE-5732:
---------------------------------------

Attached patch fixes the issue by adding a JobQueueChangeEvent that updates a Job's queue in the history.  I verified manually in addition to the tests.

> Report proper queue when job has been automatically placed
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-5732
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5732
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: MAPREDUCE-5732.patch
>
>
> Some schedulers, such as the Fair Scheduler, provide the ability to automatically place an application into a queue based on attributes such as the user and group of the submitter.  In these cases, the JobHistoryServer and AM web UI report the requested queue, not the queue that the app is actually running in.


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