Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1470526088.1221809564476.JavaMail.jira@brutus>
Date: Fri, 19 Sep 2008 00:32:44 -0700 (PDT)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4124) Changing priority of a job should be
 available in CLI and available on the web UI only along with the Kill Job
 actions
In-Reply-To: <423955444.1220943944397.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hemanth Yamijala updated HADOOP-4124:
-------------------------------------

    Attachment: HADOOP-4124.patch

Fixes a findbugs warning in the previous patch due to an incorrect test case.

test-patch output:

     [exec] +1 overall.

     [exec]     +1 @author.  The patch does not contain any @author tags.

     [exec]     +1 tests included.  The patch appears to include 6 new or modified tests.

     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.

     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.


> Changing priority of a job should be available in CLI and available on the web UI only along with the Kill Job actions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4124
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4124
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>             Fix For: 0.19.0
>
>         Attachments: HADOOP-4124.patch, HADOOP-4124.patch, HADOOP-4124.patch, HADOOP-4124.patch
>
>
> Currently, a job's priority can only be changed from the job tracker web UI. However, it is really similar (if not as destructive) as killing a job, in the sense that is should not be exposed publicly. The use case for this kind of restriction is where Hadoop is shared in production environments by different users, and they should not be allowed to change another user's priority. At the same time, it should be possible to still change a job's priority in some manner, if a user is authorized to do so, and the CLI can provide a way to do this, along with mechanisms introduced for ACLs in HADOOP-3698.

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