[
https://issues.apache.org/jira/browse/HBASE-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030154#comment-13030154
]
stack commented on HBASE-3861:
------------------------------
I just backed this out of TRUNK because its OOME'ing TestHCM up on hudson and
locally on two different platforms (I can't see why it would do it though...
must be some interaction w/ hbase-3777). It runs fine for me on branch.
> 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.90.3, 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
