[
https://issues.apache.org/jira/browse/HADOOP-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632634#action_12632634
]
Hemanth Yamijala commented on HADOOP-4124:
------------------------------------------
Ran core tests and contrib tests on my machine.
Contrib tests all passed.
Following core tests failed:
org.apache.hadoop.hdfs.server.datanode.TestBlockReplacement: This test timed
out. There is no relation to this test in the patch.
Running org.apache.hadoop.mapred.TestLimitTasksPerJobTaskScheduler: Same as
HADOOP-4213.
> 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.
