[
https://issues.apache.org/jira/browse/HBASE-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163116#comment-13163116
]
Nicolas Spiegelberg commented on HBASE-3767:
--------------------------------------------
@JD: From your description of the SynchronousQueue
{code}
Direct handoffs generally require unbounded maximumPoolSizes to avoid rejection
of new submitted tasks.
{code}
It seems like we should either add rejected task handling or not allow the user
to specify "hbase.htable.threads.max" anymore, correct?
> Improve how HTable handles threads used for multi actions
> ---------------------------------------------------------
>
> Key: HBASE-3767
> URL: https://issues.apache.org/jira/browse/HBASE-3767
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.2
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.90.3
>
> Attachments: HBASE-3767-v2.patch, HBASE-3767.patch
>
>
> When creating a new HTable we have to query ZK to learn about the number of
> region servers in the cluster. That is done for every single one of them, I
> think instead we should do it once per JVM and then reuse that number for all
> the others.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
