[
https://issues.apache.org/jira/browse/HBASE-12765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259586#comment-14259586
]
Lars Hofhansl commented on HBASE-12765:
---------------------------------------
Not sure, yet, what the best answer is. A single shared threapool might be
better. It could be initialized with a number of threads that makes sense for
the machine we're running on (umber of cores, or maybe 2x number of cores).
At least we could limit each single split transaction to never using more than
some number of threads (maybe 1/2 number of cores, or something?)
> SplitTransaction creates too many threads (potentially)
> -------------------------------------------------------
>
> Key: HBASE-12765
> URL: https://issues.apache.org/jira/browse/HBASE-12765
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> In splitStoreFiles(...) we create a new thread pool with as many threads as
> there are files to split.
> We should be able to do better. During times of very heavy write loads there
> might be a lot of files to split and multiple splits might be going on at the
> same time on the same region server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
