hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (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
Date Tue, 16 Sep 2008 06:45:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631265#action_12631265

Hemanth Yamijala commented on HADOOP-4124:

The attached patch implements the proposal above.

Specific changes:

- Introduced a new command line option in {{JobClient}} to change the priority
- Modified the Job list operation to display the Job Priority as a column so that the user
can see the current priority. In order to do so, needed to introduce a field in the {{JobStatus}}
class to hold the job's priority.
- Added a new API in {{JobSubmissionProtocol}} to change the job priority.
public void changeJobPriority(JobID jobid, String newPriority) throws IOException;
The priority is passed as a string matching the priority names. The help message of job client
lists these options for ease of use.
- Implemented same in JobTracker to call the existing {{setJobPriority}}. This includes ACL
- Modified the web UI to show priority links only if {{webinterface.private.actions}} is set
to true.
- Added new tests in {{TestJobClient}} to verify that job priority is being displayed, and
in {{TestQueueManager}} to ensure job priority change is controlled by ACLs.

Can someone please review ?

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

View raw message