whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joey Hung (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (WHIRR-339) Allow to specify hbase-site.xml properties through cluster configuration file
Date Sun, 06 Nov 2011 19:11:52 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145051#comment-13145051
] 

Joey Hung edited comment on WHIRR-339 at 11/6/11 7:11 PM:
----------------------------------------------------------

Hi Andrei,

I setup hbase-site.hbase.zookeeper.property.maxClientCnxns=100 in hbase.ec2.properties.
After the cluster runs, I check hbase-site.xml in /usr/local/hbase-0.90.4/conf and it does
show up the property correctly.
However, I can only get 10 socket connections from a single hbase client (written in java).

The rest of connections fails with these messages:
11/11/06 11:00:40 INFO zookeeper.ZooKeeper: Initiating client connection, connectString=ec2-107-22-76-61.compute-1.amazonaws.com:2181
sessionTimeout=180000 watcher=hconnection
11/11/06 11:00:40 INFO zookeeper.ClientCnxn: Opening socket connection to server ec2-107-22-76-61.compute-1.amazonaws.com/107.22.76.61:2181
11/11/06 11:00:40 INFO zookeeper.ClientCnxn: Socket connection established to ec2-107-22-76-61.compute-1.amazonaws.com/107.22.76.61:2181,
initiating session
11/11/06 11:00:41 INFO zookeeper.ClientCnxn: Unable to read additional data from server sessionid
0x0, likely server has closed socket, closing socket connection and attempting reconnect

Please help or point me to right forum for this question.
                
      was (Author: joeyhung):
    Hi Andrei,

Where should I set hbase.zookeeper.property.maxClientCnxns?
My setup:
Whirr 0.6 
3 node hbase cluster
hadoop 0.20.2 (not cdh version)
hbase 0.90.4 (not cdh version)
zookeeper-3.3.3

I tried to set this value in hbase-ec2.properties (exact duplicate from recipes), not work.
Try to set the value in hbase master node after cluster start up in hbase-site.xml, still
not work (need to restart some part of cluster?)
Try to set the value in hbase master node after cluster start up in zoo_sample.cfg, still
not work (need to restart some part of cluster?)

Currently, I can only get 10 socket connections from a single hbase client.
Please help.
                  
> Allow to specify hbase-site.xml properties through cluster configuration file
> -----------------------------------------------------------------------------
>
>                 Key: WHIRR-339
>                 URL: https://issues.apache.org/jira/browse/WHIRR-339
>             Project: Whirr
>          Issue Type: Improvement
>          Components: service/hbase
>            Reporter: Bruno Dumon
>            Assignee: Bruno Dumon
>             Fix For: 0.6.0
>
>         Attachments: WHIRR-339.patch, WHIRR-339.patch
>
>
> Currently the hbase-site.xml configuration is hardcoded in the configure(_cdh)_hbase.sh
script. This patch adds dynamic generation of hbase-site.xml, modelled after what is done
for hadoop-(common|mapred|hdfs)-site.xml.
> The user is able to specify custom properties in their cluster configuration, by prefixing
them with 'hbase-site.'
> Default config is in whirr-hbase-default.properties. Compared to what was in configure_hbase.sh
before, I dropped the setting of "hbase-site.hbase.client.retries.number=100" because I'm
not sure we should divert from the HBase default there.
> I left in the passing of the ZOOKEEPER_QUORUM to the configure script, as I figured people
using custom scripts might still want to have it (there's a PORT variable passed that doesn't
seem to be used either).
> On a more general note, this patch has the same limitations as for Hadoop: running master
and regionserver on same node will not work as the configuration will be appended twice to
the same file, and running the restserver/thriftserver not together with regionserver or master
will fail due to missing hbase-site.xml. Solving this is a topic of its own.

--
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

        

Mime
View raw message