Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 19 Dec 2011 07:00:31 +0000 (UTC)
From: "Lars Hofhansl (Resolved) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1061877918.25239.1324278031896.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1471978059.48122.1323226060197.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HBASE-4970) Add a parameter so that
 keepAliveTime of Htable thread pool can be changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl resolved HBASE-4970.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.92.1
                   0.94.0
     Hadoop Flags: Reviewed

Committed to 0.90, 0.92, and trunk.
Thanks for the patch and your patience, gaojinchao.

                
> Add a parameter so that keepAliveTime of Htable thread pool can be changed
> --------------------------------------------------------------------------
>
>                 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.94.0, 0.92.1, 0.90.6
>
>         Attachments: HBASE-4970_Branch90.patch, HBASE-4970_Branch90_V1_trial.patch, HBASE-4970_Branch90_V2.patch, HBASE-4970_Branch92_V2.patch, HBASE-4970_Trunk_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