[
https://issues.apache.org/jira/browse/HADOOP-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1433:
---------------------------------
Status: Open (was: Patch Available)
This looks reasonable to me too. Unfortunately it no longer passes unit tests,
e.g., TestMiniMRLocalFS failing with:
{code}
java.io.IOException: java.lang.NullPointerException
at org.apache.hadoop.mapred.JobTracker$2.compare(JobTracker.java:1477)
at org.apache.hadoop.mapred.JobTracker$2.compare(JobTracker.java:1476)
at java.util.Arrays.mergeSort(Arrays.java:1284)
at java.util.Arrays.sort(Arrays.java:1223)
at java.util.Collections.sort(Collections.java:159)
at
org.apache.hadoop.mapred.JobTracker.resortPriority(JobTracker.java:1490)
at org.apache.hadoop.mapred.JobTracker.submitJob(JobTracker.java:1462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)
{code}
> 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
> Assignee: Johan Oskarsson
> Priority: Minor
> Fix For: 0.14.0
>
> Attachments: jobpriorityv2.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.
