[
https://issues.apache.org/jira/browse/HBASE-18735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703508#comment-16703508
]
Artem Ervits commented on HBASE-18735:
--------------------------------------
[~jamestaylor] it's hard to say as I imagine the proportion of improvement is
tied to number of tables and rows ingested. I originally tested with 1, 10 and
100 tables. Improvement was 1 second faster for 1 table, 5 seconds or so for 10
tables and 50 seconds for 100 tables. On 100 tables, improvement is 12%. If you
want to identify a few tests in Phoenix to test this on, I will be happy to
take this upon myself, let's do this in a Phoenix Jira, feel free to assign to
me?
> 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)
