You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2009/01/16 12:08:00 UTC
[jira] Updated: (HADOOP-4832) Have end to end tests based on
MiniMRCluster to verify the correct behaviour of job priorities.
[ https://issues.apache.org/jira/browse/HADOOP-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod K V updated HADOOP-4832:
------------------------------
Attachment: HADOOP-4832-20090116.txt
Attaching patch for review.
> Have end to end tests based on MiniMRCluster to verify the correct behaviour of job priorities.
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-4832
> URL: https://issues.apache.org/jira/browse/HADOOP-4832
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Vinod K V
> Assignee: Vinod K V
> Attachments: HADOOP-4832-20090116.txt
>
>
> We should have the following tests:
> - Basic priority test: submit jobs with different priorities and verify their proper ordering and running.
> - New jobs with higher priority are submitted: verify that they are inserted at right positions in the queue and that they run accordingly.
> - Changing the priority of an existing waiting job: verify that the order of jobs is rehashed.
> - Changing the priority of an existing running job: verify that the order of jobs is rehashed and that running of the jobs is affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.