[
https://issues.apache.org/jira/browse/HBASE-23647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021607#comment-17021607
]
Bharath Vissapragada commented on HBASE-23647:
----------------------------------------------
[~apurtell] {{TestFromClientSide}} was known to be flaky (even before this
patch). So I'm fairly certain it has nothing to do with the current jira.
One thing [~ndimiduk] and I noticed here is that switching to JUnit 4.13
(HBASE-23664) has exacerbated the problem. Based on some initial debugging it
looks like it has something to do with leaking FileSystem/DFSClient objects in
the HBase code and restarting the minicluster in the same JUnit test runner JVM
(what TestFromClientSide does) causes a leak of hdfs lease renewer threads.
Some how Junit 4.12 was masking the problem.
> Make MasterRegistry the default registry impl
> ---------------------------------------------
>
> Key: HBASE-23647
> URL: https://issues.apache.org/jira/browse/HBASE-23647
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Affects Versions: 3.0.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Major
>
> Now that we are close to getting the registry implementation patch in, the
> idea here is to make it the default implementation in 3.0.0 and this means
> - No known bugs with the implementation
> - No known performance issues
> - Entire nightly test suite is green (and without flakes).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
