On Thu, Jun 7, 2012 at 1:31 PM, Mohammad Tariq <dontariq@gmail.com&g= t; wrote:

Actually zookeeper servers have an active co= nnections limit, which by
default is 30. You can increase this limit by setting maxClientCnxns
property accordingly in your zookeeper config file, zoo.cfg. For
example - maxClientCnxns=3D100....but before that copy the
hadoop-core-*.jar present inside hadoop folder to the hbase/lib
folder.Also copy commons-configuration-1.6.jar from hadoop/lib folder
to hbase/lib folder and check it once and see if it works for you.

Regards,
=A0=A0 =A0Mohammad Tariq

On Thu, Jun 7, 2012 at 1:13 PM, Manu S <manupkd87@gmail.com> wrote:
> Hi All,
>
> Thank you for your reply.
>
> I tried all these options but still I am facing this issue.
>
> @Mayank: I tried the same, but still getting error.
> export
> HADOOP_CLASSPATH=3D"/usr/lib/hadoop/:/usr/lib/hadoop/lib/:/usr/li= b/hadoop/conf/"
> export
> HBASE_CLASSPATH=3D"/usr/lib/hbase/:/usr/lib/hbase/lib/:/usr/lib/h= base/conf/:/usr/lib/zookeeper/:/usr/lib/zookeeper/conf/:/usr/lib/zookeeper/= lib/"
> export CLASSPATH=3D"${HADOOP_CLASSPATH}:${HBASE_CLASSPATH}"<= br> >
> @Marcos & Tariq:
> We are using Hbase version 0.90.4
> Job creating single HBaseConfiguration object only
>
> @Kevin:
> No luck, same error
>
>
> Thanks,
> Manu S
>
> On Thu, Jun 7, 2012 at 3:50 AM, Mayank Bansal <mayank@apache.org> wrote:
>
>>
>> zookeeper conf is not on the class path for the mapreduce job. Add= conf
>>> file to class path for the job.
>>>
>>> Thanks,
>>> Mayank
>>>
>>>
>>> On Wed, Jun 6, 2012 at 7:25 AM, Manu S <manupkd87@gmail.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We are running a mapreduce job in a fully distributed clus= ter.The output
>>>> of the job is writing to HBase.
>>>>
>>>> While running this job we are getting an error:
>>>>

>>>> *Caused by: org.apache.hadoop.hbase.ZooKeeperC= onnectionException: HBase is able to connect to ZooKeeper but the connectio= n closes immediately. This could be a sign that the server has too many con= nections (30 is the default). Consider inspecting your ZK server logs for t= hat error and then make sure you are reusing HBaseConfiguration as often as= you can. See HTable's javadoc for more information.*

>>>> =A0 =A0 at org.apache.hadoop.hbase.zooke= eper.ZooKeeperWatcher.<init>(ZooKeeperWatcher.java:155)
>>>> =A0 =A0 at org.apache.hadoop.hbase.client.HConnectionManag= er$HConnectionImplementation.getZooKeeperWatcher(HConnectionManager.java:10= 02)
>>>> =A0 =A0 at org.apache.hadoop.hbase.client.HConnectionManag= er$HConnectionImplementation.setupZookeeperTrackers(HConnectionManager.java= :304)
>>>> =A0 =A0 at org.apache.hadoop.hbase.client.HConnectionManag= er$HConnectionImplementation.<init>(HConnectionManager.java:295)
>>>> =A0 =A0 at org.apache.hadoop.hbase.client.HConnectionManag= er.getConnection(HConnectionManager.java:157)
>>>> =A0 =A0 at org.apache.hadoop.hbase.client.HTable.<init&= gt;(HTable.java:169)
>>>> =A0 =A0 at org.apache.hadoop.hbase.client.HTableFactory.cr= eateHTableInterface(HTableFactory.java:36)
>>>>
>>>>
>>>> I had gone through some threads related to this issue and = I modified the

>>>> *zoo.cfg* accordingly. These configurations are same= in all the nodes.

>>>> Please find the configuration of HB= ase & ZooKeeper:
>>>>
>>>> Hbase-site.xml:
>>>>
>>>> <configuration>
>>>>
>>>> <property>
>>>> <name>hbase.cluster.distributed</name>
>>>> <value>true</value>
>>>> </property>
>>>>
>>>> <property>
>>>> <name>hbase.rootdir</name>
>>>> <value>hdfs://namenode/hbase</value>
>>>> </property>
>>>>
>>>> <property>
>>>> <name>hbase.zookeeper.quorum</name>
>>>> <value>namenode</value>
>>>> </property>
>>>>
>>>> </configuration>
>>>>
>>>>
>>>> Zoo.cfg:
>>>>
>>>> # The number of milliseconds of each tick
>>>> tickTime=3D2000
>>>> # The number of ticks that the initial
>>>> # synchronization phase can take
>>>> initLimit=3D10
>>>> # The number of ticks that can pass between
>>>> # sending a request and getting an acknowledgement
>>>> syncLimit=3D5
>>>> # the directory where the snapshot is stored.
>>>> dataDir=3D/var/zookeeper
>>>> # the port at which the clients will connect
>>>> clientPort=3D2181
>>>> #server.0=3Dlocalhost:2888:3888
>>>> server.0=3Dnamenode:2888:3888
>>>>
>>>> ################# Max Client connections #################= ##

>>>> *maxClientCnxns=3D1000
>>>> minSessionTimeout=3D4000
>>>> maxSessionTimeout=3D40000*

>>>>
>>>>
>>>> It would be really great if anyone can help me to resolve = this issue by
>>>> giving your thoughts/suggestions.
>>>>
>>>> Thanks,
>>>> Manu S
>>>>
>>>
>>>
>>