[
https://issues.apache.org/jira/browse/HBASE-18735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701993#comment-16701993
]
Artem Ervits commented on HBASE-18735:
--------------------------------------
.02 patch addresses [~stack] comment as well as fixes some checkstyle issues.
There are over 7000 checkstyle issues in hbase-server and hundreds of issues in
HBaseTestingUtility alone, if need be, I can address those in a separate jira.
My question remains, is this a useful patch [~jamestaylor] [~lhofhansl] and do
I need to keep the tests as they're not testing but merely there for timing
purposes. [~elserj] please advise.
> Provide a fast mechanism for shutting down mini cluster
> -------------------------------------------------------
>
> Key: HBASE-18735
> URL: https://issues.apache.org/jira/browse/HBASE-18735
> Project: HBase
> Issue Type: Wish
> Reporter: Samarth Jain
> Assignee: Artem Ervits
> Priority: Major
> Attachments: HBASE-18735.v01.patch, HBASE-18735.v02.patch
>
>
> The current mechanism of shutting down a mini cluster through
> HBaseTestingUtility.shutDownMiniCluster can take a lot of time when the mini
> cluster almost has a lot of tables. A lot of this time is spent in closing
> all the user regions. It would be nice to have a mechanism where this
> shutdown can happen quickly without having to worry about closing these user
> regions. At the same time, this mechanism would need to make sure that all
> the critical system resources like file handles and network ports are still
> released so that subsequently initialized mini clusters on the same JVM or
> system won't run into resource issues. This would make testing using HBase
> mini clusters much faster and immensely help out test frameworks of dependent
> projects like Phoenix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
