hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Gao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4271) Make TestCapacityScheduler more robust with non-Sun JDK
Date Wed, 07 Nov 2012 19:12:12 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492603#comment-13492603

Yu Gao commented on MAPREDUCE-4271:

The patch fixed the failure of testMultiTaskAssignmentInMultipleQueues and testQueueOrdering
with IBM JDK.

The NullPointException problem seems to be tracked by MAPREDUCE-4699
Testcase: testHighPriorityJobInitialization took 1.412 sec
	Caused an ERROR
	at org.apache.hadoop.mapred.JobHistory$JobInfo.logJobPriority(JobHistory.java:1969)
	at org.apache.hadoop.mapred.JobInProgress.setPriority(JobInProgress.java:895)
	at org.apache.hadoop.mapred.TestCapacityScheduler$FakeTaskTrackerManager.setPriority(TestCapacityScheduler.java:653)
	at org.apache.hadoop.mapred.TestCapacityScheduler.testHighPriorityJobInitialization(TestCapacityScheduler.java:2666)

> Make TestCapacityScheduler more robust with non-Sun JDK
> -------------------------------------------------------
>                 Key: MAPREDUCE-4271
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4271
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: capacity-sched
>    Affects Versions: 1.0.3
>            Reporter: Luke Lu
>            Assignee: Yu Gao
>              Labels: alt-jdk, capacity
>         Attachments: mapreduce-4271-branch-1.patch, test-afterepatch.result, test-beforepatch.result,
> The capacity scheduler queue is initialized with a HashMap, the values of which are later
added to a list (a queue for assigning tasks). TestCapacityScheduler depends on the order
of the list hence not portable across JDKs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message