[
https://issues.apache.org/jira/browse/HBASE-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383351#comment-14383351
]
Mikhail Antonov commented on HBASE-13252:
-----------------------------------------
It's getting better..
Tests run: 18, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 198.478 sec
<<< FAILURE! - in org.apache.hadoop.hbase.master.TestDistributedLogSplitting
testLogReplayTwoSequentialRSDown(org.apache.hadoop.hbase.master.TestDistributedLogSplitting)
Time elapsed: 37.21 sec <<< FAILURE!
java.lang.AssertionError: expected:<1000> but was:<891>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
That's the only test which failed, and this failure doesn't look like something
caused by connection rewiring..gonna retry.
> Get rid of managed connections and connection caching
> -----------------------------------------------------
>
> Key: HBASE-13252
> URL: https://issues.apache.org/jira/browse/HBASE-13252
> Project: HBase
> Issue Type: Sub-task
> Components: API
> Affects Versions: 2.0.0
> Reporter: Mikhail Antonov
> Assignee: Mikhail Antonov
> Attachments: HBASE-13252-v0.patch, HBASE-13252-v1.patch,
> HBASE-13252-v1.patch, HBASE-13252-v2.patch
>
>
> (Need to):
> - Remove CONNECTION_INSTANCES from ConnectionManager
> - Remove HConnectionKey
> - Remove 'managed' property from ClusterConnection, HCI and places where
> it's used now
> - AFAIS this property isn't visible to client (ClusterConnection is private
> interface), so technically this would not even be backward-incompatible
> change, and no release note needed?
> - In fact, ConnectionManager can be removed, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
