[
https://issues.apache.org/jira/browse/HBASE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776785#comment-13776785
]
Jean-Daniel Cryans commented on HBASE-9333:
-------------------------------------------
Did more testing, even went back to RC3 to verify a few things and here is what
I saw:
- *RC3*: client uses loads of threads and OOMEs with a default heap.
- *9609*: seems to be using almost as many threads (it seems more spikier, but
the spikes are never as bad as RC3), but with 1/3 of the default heap used.
- *9609+9333*: now the number of threads is fixed to 256 by default (and the
AsyncProcess tasks are queued above that).
Performance seems to be about the same when the client is able to finish.
> hbase.hconnection.threads.max should not be configurable else you get
> RejectedExecutionException
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-9333
> URL: https://issues.apache.org/jira/browse/HBASE-9333
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.95.2
> Reporter: Jean-Daniel Cryans
> Assignee: Elliott Clark
> Priority: Critical
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9333.v1.patch, HBASE-9333-0.patch, HBASE-9333-1.patch,
> HBASE-9333-2.patch
>
>
> Trying to set hbase.hconnection.threads.max to a lower number than its
> default of Integer.MAX_VALUE simply results in a RejectedExecutionException
> when the max is reached. It seems there's no good reason to keep this
> configurable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
