[
https://issues.apache.org/jira/browse/HBASE-19299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258344#comment-16258344
]
Hudson commented on HBASE-19299:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4079 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4079/])
HBASE-19299 Assert only one Connection is constructed when calculating (stack:
rev b4fbf5fe18bc9247106f674580666096fd34d3fa)
* (add)
hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/mapreduce/TestMultiTableInputFormatBase.java
> Assert only one Connection is constructed when calculating splits in a
> MultiTableInputFormat
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-19299
> URL: https://issues.apache.org/jira/browse/HBASE-19299
> Project: HBase
> Issue Type: Test
> Components: test
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments:
> 0002-HBASE-19299-Assert-only-one-Connection-is-constructe.patch
>
>
> Small test that verifies only one Connection made when calculating splits. We
> used to put up one per Table until recently and before that, a Connection per
> table per split which put a heavy load on hbase;meta. Here is a test to
> ensure we don't go back to the bad-old-days.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
