[
https://issues.apache.org/jira/browse/HBASE-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167684#comment-13167684
]
Lars Hofhansl commented on HBASE-4970:
--------------------------------------
Hmm... I am -0 on the extra config option. I really think that should be some
slightly configurable default behavior, and if that does not fit the
requirements, one should manage the ExecutorService separately rather than
adding more and more config options.
I'm not opposed, though.
In either case, if we did the config option part, that part would need to be
added to 0.92 and trunk as well.
If we did the config option part, does it still make sense to backport my
0.92/trunk change?
gaojinchao, if you had both options at your disposal (separate ExecutorService
and your config option), which one would you use? We should do that one thing
that you would use.
> Allow better control of resource consumption in HTable (backport HBASE-4805
> to 0.90 branch)
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-4970
> URL: https://issues.apache.org/jira/browse/HBASE-4970
> Project: HBase
> Issue Type: Improvement
> Components: client
> Affects Versions: 0.90.4
> Reporter: gaojinchao
> Assignee: gaojinchao
> Priority: Trivial
> Fix For: 0.90.6
>
> Attachments: HBASE-4970_Branch90.patch,
> HBASE-4970_Branch90_V1_trial.patch, HBASE-4970_Branch90_V2.patch
>
>
> In my cluster, I changed keepAliveTime from 60 s to 3600 s. Increasing RES
> is slowed down.
> Why increasing keepAliveTime of HBase thread pool is slowing down our problem
> occurance [RES value increase]?
> You can go through the source of sun.nio.ch.Util. Every thread hold 3
> softreference of direct buffer(mustangsrc) for reusage. The code names the 3
> softreferences buffercache. If the buffer was all occupied or none was
> suitable in size, and new request comes, new direct buffer is allocated.
> After the service, the bigger one replaces the smaller one in buffercache.
> The replaced buffer is released.
> So I think we can add a parameter to change keepAliveTime of Htable thread
> pool.
--
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
