hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gopal V (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4699) TestFairScheduler & TestCapacityScheduler fails due to JobHistory exception
Date Tue, 02 Oct 2012 22:21:08 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gopal V updated MAPREDUCE-4699:
-------------------------------

    Attachment: mapreduce-4699.patch

Patch to call JobTracker init in the helper class
                
> TestFairScheduler & TestCapacityScheduler fails due to JobHistory exception
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4699
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4699
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Gopal V
>            Priority: Minor
>         Attachments: mapreduce-4699.patch
>
>
> TestFairScheduler fails due to exception from mapred.JobHistory
> {code}
> null
> java.lang.NullPointerException
> 	at org.apache.hadoop.mapred.JobHistory$JobInfo.logJobPriority(JobHistory.java:1975)
> 	at org.apache.hadoop.mapred.JobInProgress.setPriority(JobInProgress.java:895)
> 	at org.apache.hadoop.mapred.TestFairScheduler.testFifoPool(TestFairScheduler.java:2617)
> {code}
> TestCapacityScheduler fails due to
> {code}
> java.lang.NullPointerException
>     at org.apache.hadoop.mapred.JobHistory$JobInfo.logJobPriority(JobHistory.java:1976)
>     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)
> {code}

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

Mime
View raw message