Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 69001 invoked from network); 17 Jan 2010 20:17:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jan 2010 20:17:07 -0000 Received: (qmail 7339 invoked by uid 500); 17 Jan 2010 20:17:07 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 7299 invoked by uid 500); 17 Jan 2010 20:17:07 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 7100 invoked by uid 99); 17 Jan 2010 20:17:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jan 2010 20:17:07 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.211.187 as permitted sender) Received: from [209.85.211.187] (HELO mail-yw0-f187.google.com) (209.85.211.187) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jan 2010 20:17:00 +0000 Received: by ywh17 with SMTP id 17so1815633ywh.2 for ; Sun, 17 Jan 2010 12:16:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=h3bV8kGY483E5yQm5bK+30Q69XEj5xgejm0lLV+uPeQ=; b=vsU/h3Bq+T1rporkPJGn2ekFAhsCKW6tiXPOHgrw+MuLgw7fRiNJdVvSxdDCUeraNo /OygbJPBTtuVDu2oryh67b28Br2kzdyhzPuL6dZyrQG3nNEc8cxa48PcRxApsg1laSOH xcHRY/O2Llo5WcWvQRojr6s7+ZmeQQApIuPlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=M5xdJ4N6vils0kzMNvIrwTquTIZ3sFgo4CJfmuU0tPsW06e8QmIFCHNRG1/gZUsRlS OwLUa8ZhLV3oo6DzCT8TmBWuxF0Kl/ixyiybTNRSfXM5k3OPqzx1TThZeBfCB6hf8qTC jQSE7UiNDYG59KqEKhuq2dkhAvkfmJCHf1Bvo= MIME-Version: 1.0 Sender: jdcryans@gmail.com Received: by 10.91.136.9 with SMTP id o9mr4187587agn.111.1263759399155; Sun, 17 Jan 2010 12:16:39 -0800 (PST) In-Reply-To: <685845.84546.qm@web65508.mail.ac4.yahoo.com> References: <1573609277.271681263583254710.JavaMail.jira@brutus.apache.org> <1587559853.283201263603774446.JavaMail.jira@brutus.apache.org> <61770b881001171017l14d60499ofb0e27c6afcea4a@mail.gmail.com> <7c962aed1001171156y27aa77acm8fbf0a1948eae92e@mail.gmail.com> <685845.84546.qm@web65508.mail.ac4.yahoo.com> Date: Sun, 17 Jan 2010 12:16:39 -0800 X-Google-Sender-Auth: 50bfd4f58f5cafb2 Message-ID: <31a243e71001171216p8bed6c4od0c7336abd63d93@mail.gmail.com> Subject: Re: [jira] Resolved: (HBASE-2133) Increase default number of client handlers From: Jean-Daniel Cryans To: hbase-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable +1 J-D On Sun, Jan 17, 2010 at 12:12 PM, Andrew Purtell wrot= e: >> We could add a metric that did an iteration of handlers in HBaseServer >> emitting how many were in progress. =A0There is no provision for doing t= his >> currently. =A0Would have to add accessors, etc. > > If already going into the code and changing things... > > Having a bounded thread pool is important, so availability can degrade > gracefully (more or less), as opposed to the whole regionserver becoming > livelocked. But, we don't need for the pool to be preallocated as is > done currently. How about changing the RPC server thread pool such that > the user can specify a minimum and maximum number of handler threads? The > pool would start with the minimum, allocate more up to the max to handle > additional concurrency, then terminate unused threads after some time > back down to the minimum. Then we can do things like set a maximum of 100 > handlers or such without taking on the overhead of 100 threads until it > is needed. > > =A0 - Andy > > > > ----- Original Message ---- >> From: stack >> To: hbase-dev@hadoop.apache.org >> Sent: Sun, January 17, 2010 11:56:45 AM >> Subject: Re: [jira] Resolved: (HBASE-2133) Increase default number of cl= ient =A0handlers >> >> We could add a metric that did an iteration of handlers in HBaseServer >> emitting how many were in progress. =A0There is no provision for doing t= his >> currently. =A0Would have to add accessors, etc. =A0Its a good idea. =A0A= s a >> metric, we might miss a burst of requests filling all slots but sustaine= d >> high request numbers would show. >> >> St.Ack >> >> On Sun, Jan 17, 2010 at 10:17 AM, Lars George wrote: >> >> > Hi Andrew, >> > >> > I have it at 30. What I would like to know is how to detect this sort >> > of shortage? I also have the feeling we need this sort of indicators >> > as metrics to the various servers so that the max and current can be >> > graphed. What do you think? >> > >> > Thanks, >> > Lars >> > >> > On Sat, Jan 16, 2010 at 2:02 AM, Andrew Purtell (JIRA) >> > wrote: >> > > >> > > =A0 =A0 [ >> > >> https://issues.apache.org/jira/browse/HBASE-2133?page=3Dcom.atlassian.ji= ra.plugin.system.issuetabpanels:all-tabpanel] >> > > >> > > Andrew Purtell resolved HBASE-2133. >> > > ----------------------------------- >> > > >> > > =A0 =A0 =A0Resolution: Fixed >> > > =A0 =A0Hadoop Flags: [Reviewed] >> > > >> > > Committed following change to trunk and 0.20 branch: >> > > \\ >> > > {noformat} >> > > --- conf/hbase-default.xml =A0 =A0 =A0(revision 899849) >> > > +++ conf/hbase-default.xml =A0 =A0 =A0(working copy) >> > > @@ -153,10 +153,10 @@ >> > > >> > > >> > > =A0 =A0hbase.regionserver.handler.count >> > > - =A0 =A010 >> > > + =A0 =A025 >> > > =A0 =A0Count of RPC Server instances spun up on RegionServers >> > > =A0 =A0 Same property is used by the HMaster for count of master han= dlers. >> > > - =A0 =A0Default is 10. >> > > + =A0 =A0Default is 25. >> > > >> > > >> > > >> > > {noformat} >> > > >> > > We might want to increase this again depending on user feedback. I k= now I >> > needed 100 to avoid trouble with high read/write load once above ~200 >> > regions/server. >> > > >> > >> Increase default number of client handlers >> > >> ------------------------------------------ >> > >> >> > >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: HBASE-2133 >> > >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/jira= /browse/HBASE-2133 >> > >> =A0 =A0 =A0 =A0 =A0 =A0 Project: Hadoop HBase >> > >> =A0 =A0 =A0 =A0 =A0Issue Type: Improvement >> > >> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Andrew Purtell >> > >> =A0 =A0 =A0 =A0 =A0 =A0Assignee: Andrew Purtell >> > >> =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 0.20.3, 0.21.0 >> > >> >> > >> >> > >> Any reason not to just go ahead and change hbase-default.xml to inc= lude: >> > >> {noformat} >> > >> >> > >> =A0 =A0hbase.regionserver.handler.count >> > >> =A0 =A0100 >> > >> >> > >> >> > >> =A0 =A0hbase.zookeeper.property.maxClientCnxns >> > >> =A0 =A0100 >> > >> >> > >> {noformat} >> > >> ? >> > >> The current default for both, 10, is anemic. >> > > >> > > -- >> > > This message is automatically generated by JIRA. >> > > - >> > > You can reply to this email to add a comment to the issue online. >> > > >> > > >> > > > > > > >