Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B7F7D4888 for ; Thu, 19 May 2011 21:38:30 +0000 (UTC) Received: (qmail 13616 invoked by uid 500); 19 May 2011 21:38:30 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 13576 invoked by uid 500); 19 May 2011 21:38:30 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 13568 invoked by uid 99); 19 May 2011 21:38:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 21:38:30 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 21:38:27 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 83E33D18FC for ; Thu, 19 May 2011 21:37:47 +0000 (UTC) Date: Thu, 19 May 2011 21:37:47 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: <517125539.28384.1305841067536.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <47702671.26550.1304636583162.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HBASE-3861) MiniZooKeeperCluster.startup() should refer to hbase.zookeeper.property.maxClientCnxns MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3861: ------------------------- Fix Version/s: (was: 0.90.4) Moving this to 0.92.0. It was committed for 0.90.3. > MiniZooKeeperCluster.startup() should refer to hbase.zookeeper.property.maxClientCnxns > -------------------------------------------------------------------------------------- > > Key: HBASE-3861 > URL: https://issues.apache.org/jira/browse/HBASE-3861 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.90.3 > Reporter: Eugene Koontz > Assignee: Eugene Koontz > Fix For: 0.92.0 > > Attachments: HBASE-3861.patch, HBASE-3861.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Currently the number of the client connections is hard-wired to 1000: > {{{ > standaloneServerFactory = new NIOServerCnxnFactory(); > standaloneServerFactory.configure(new InetSocketAddress(clientPort),1000); > } catch (BindException e) { > > }}} > This should be set according to the test environment's hbase configuration. The property in > question is : hbase.zookeeper.property.maxClientCnxns. > Currently some tests such as org.apache.hadoop.hbase.client.TestHCM fail because the number of connections used by the HBase client exceeds 1000. > Recently MAX_CACHED_HBASE_INSTANCES increased from 31 to 2000 on 0.90 branch: > http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.java&p1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fhadoop%2Fhbase%2Fclient%2FHConnectionManager.java&r1=1096818&r2=1096817&view=diff&pathrev=1096818 > and correspondingly the hbase config on the Zookeeper server-side also increased in hbase-default.xml: > http://svn.apache.org/viewvc/hbase/branches/0.90/src/main/resources/hbase-default.xml?p2=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fresources%2Fhbase-default.xml&p1=%2Fhbase%2Fbranches%2F0.90%2Fsrc%2Fmain%2Fresources%2Fhbase-default.xml&r1=1091594&r2=1091593&view=diff&pathrev=1091594 > So if MiniZKCluster looks at this setting, the test won't have this failure. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira