hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8326) mapreduce.TestTableInputFormatScan times out frequently
Date Sat, 13 Apr 2013 01:31:13 GMT

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

Nick Dimiduk commented on HBASE-8326:
-------------------------------------

bq. What explains the ~200 additional seconds of wall clock time required by the test after
HBASE-8158?

The test includes 12 {{@Test}} annotated methods, each invoking this code-path, which accounts
for ~50 total additional seconds for the test. If these Jenkins host are so overloaded as
you say, a 4x slowdown vs my MBA (which has an SSD) is entirely plausible.

[~apurtell] can you pull this log from an arbitrary Jenkins build for analysis? The grep incantation
in my previous comment will pull the data we need.
                
> mapreduce.TestTableInputFormatScan times out frequently
> -------------------------------------------------------
>
>                 Key: HBASE-8326
>                 URL: https://issues.apache.org/jira/browse/HBASE-8326
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce, test
>    Affects Versions: 0.98.0, 0.94.7, 0.95.1
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>
> bq. It looks like since this change org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan
has not passed a single time in the EC2 builds (http://54.241.6.143/job/HBase-0.94/). Change
was introduced in Build #72, since then this tests times out (or doesn't finish)
> via [~lhofhansl] in [HBASE-8140 comment|https://issues.apache.org/jira/browse/HBASE-8140?focusedCommentId=13629101&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13629101].

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