hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7681) Increase timeouts in some more test...?
Date Sat, 26 Jan 2013 18:43:12 GMT

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

Lars Hofhansl commented on HBASE-7681:

In the latest run I see this a failure in TestImportTsv caused by this:
2013-01-26 18:05:13,972 ERROR [pool-30-thread-1] mapred.JobTracker(4228): Job initialization
java.io.IOException: Number of maps in JobConf doesn't match number of recieved splits for
job job_20130126180500315_0001! numMapTasks=2, #splits=1
	at org.apache.hadoop.mapred.JobInProgress.initTasks(JobInProgress.java:703)
	at org.apache.hadoop.mapred.JobTracker.initJob(JobTracker.java:4207)
	at org.apache.hadoop.mapred.EagerTaskInitializationListener$InitJob.run(EagerTaskInitializationListener.java:79)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

> Increase timeouts in some more test...?
> ---------------------------------------
>                 Key: HBASE-7681
>                 URL: https://issues.apache.org/jira/browse/HBASE-7681
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>             Fix For: 0.94.5
>         Attachments: 7681-0.94.txt
> I've seen many unspecific test failures recently that cannot be reproduced locally even
when running these test is a loop for a very long time.
> Many of these test one way or the other make assumption w.r.t. wall clock time. While
I cannot fix that, an option to increase some of these timeout a bit.
> This issue is to remind me to do that.

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