[
https://issues.apache.org/jira/browse/HBASE-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630399#comment-13630399
]
Nick Dimiduk commented on HBASE-8326:
-------------------------------------
This looks isolated to the test environment, but I need more exhaustive testing
to confirm. Current observation is that the maven test environment doesn't
involve any HBase jars in the classpath. The updated logic forces providing a
jar in all cases. Thus, in the test environment we have {{JarFinder}} packaging
up a jar for each HBase class listed by
{{TableMapReduceUtil#addDependencyJars}}. This IO added a measurable amount of
time to that part of the code.
I didn't observe this behavior in my integration testing precisely because I
designed the integration test environment to build classpaths based on jars (a
closer mock of the production env) instead of relying on maven to include
classes dir in the classpath.
bq. I think we should ... and also put TestTableInputFormatScan on a diet.
[~apurtell] please advise regarding what that diet might look like, I'll put
something together.
> 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
