[
https://issues.apache.org/jira/browse/HADOOP-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Oskarsson updated HADOOP-1433:
------------------------------------
Attachment: jobpriorityv1-trunk.patch
This patch adds a jobconf setting and web ui controls for changing the priority
of a job.
It then sorts the collection containing the jobs by this priority and then by
start date.
Hadoop picks the first job in this list and starts running tasks from that job.
There might be situations where all reduce task slots have already been
assigned. the user then increases the priority on another job. that job can not
be assigned reducers until the previous jobs have released theirs.
I've left this as is for now, but there's room for improvements down the road.
Passes all unit tests on my machine.
> Add job priority
> ----------------
>
> Key: HADOOP-1433
> URL: https://issues.apache.org/jira/browse/HADOOP-1433
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred
> Affects Versions: 0.14.0
> Reporter: Johan Oskarsson
> Priority: Minor
> Fix For: 0.14.0
>
> Attachments: jobpriorityv1-trunk.patch
>
>
> As more and more developers start using our cluster we run into problems
> where big low priority jobs block smaller high priority ones.
> A simple way of specifying the job priority in the JobConf and perhaps even
> change it during runtime via the jobtracker web ui would help a lot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
