[
https://issues.apache.org/jira/browse/HBASE-18735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703850#comment-16703850
]
Josh Elser commented on HBASE-18735:
------------------------------------
Sounds good enough to me. I don't see an obvious reason why your change would
have any direct impact on TestMultiColumnScanner.
Let's try this on master and 2.x? Would say we can put it on Master only, but I
don't think we have a corresponding Phoenix build for HBase 3 yet.
> 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,
> HBASE-18735.v03.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)
