Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@locus.apache.org Received: (qmail 99160 invoked from network); 22 Oct 2008 10:27:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Oct 2008 10:27:30 -0000 Received: (qmail 40538 invoked by uid 500); 22 Oct 2008 10:27:32 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 40517 invoked by uid 500); 22 Oct 2008 10:27:31 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 40506 invoked by uid 99); 22 Oct 2008 10:27:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Oct 2008 03:27:31 -0700 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 michael.dagaev@gmail.com designates 72.14.220.155 as permitted sender) Received: from [72.14.220.155] (HELO fg-out-1718.google.com) (72.14.220.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Oct 2008 10:26:22 +0000 Received: by fg-out-1718.google.com with SMTP id l26so263638fgb.35 for ; Wed, 22 Oct 2008 03:26:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=+AOlDF1TkTX7KsWVyuVy3rbLj+oo8rCmCTJ4Kyc3dSY=; b=kDXy1T/3oWDKEEkXET5oRkw7EnaD8MZTdzGeA1Pi36dsX4rvgEOfDvZ7UMB9Jo2v4O JgjfDQbTEdqwY3V6XerrlCG4lErXdB7hHzD/VidRndRyIUcb7wRhSRFyuJYs0GdHaMq2 GcQhWn9l1+AbKemmrOfE3kb40kGNws9453Q/Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=vElg5Pxjeh+LPehmqYPTG6OQ4RNsV5yHobKfmhorFoJOOwlTOSHezcEmYxzp5wDZ/o h0yXxc9ehcd9ogerAnQfUqsL1PON9DkLgrkNbsylZDt7OdY0OKp+H89tiPU0cJINGCB4 BdGMrERO1IPfpuVLVws0sSeP4Zyks3j+w1jGw= Received: by 10.187.218.12 with SMTP id v12mr1449721faq.22.1224671209994; Wed, 22 Oct 2008 03:26:49 -0700 (PDT) Received: by 10.187.194.11 with HTTP; Wed, 22 Oct 2008 03:26:49 -0700 (PDT) Message-ID: <2f81e00810220326n757eea18s54569e1c313b2751@mail.gmail.com> Date: Wed, 22 Oct 2008 12:26:49 +0200 From: "Michael Dagaev" To: hbase-user@hadoop.apache.org Subject: Question on Connection Pooling MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi, All As I understand, HConnectionManager class pools table server connections (HBASE_INSTANCES) but does not pool connections to the master server. Is it correct? I guess it is implemented this way since the master serves many clients and may run of connections. On the other hand, what if there are only few clients ? Doesn't it make sense to make this behavior configurable ? I have noticed that the table server connection pool does not have min. and max. number of connections. Don't you think it would be nice to add it? Thank you for your cooperation, M.