Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # user >> Zookeeper Implementation


Copy link to this message
-
Re: Zookeeper Implementation
You are giving the names of all the zookeeper nodes in accumulo-site.xml,
right?

  <property>
    <name>instance.zookeeper.host</name>
    <value>zoo1,zoo2,zoo3,zoo4,zoo5</value>
  </property>

Have you increased maxClientCnxns as described in the accumulo README?

-Eric

On Mon, Jul 15, 2013 at 2:04 PM, Drew Thornton
<[EMAIL PROTECTED]>wrote:

>  Hello,****
>
> ** **
>
> I’m running a small cluster of 10 tablet servers and 5 zookeeper nodes
> (CDH 4.3, Zookeeper 3.4.5, Accumulo 1.5.0).****
>
> ** **
>
> I have noticed that when a zookeeper node dies, the connected tablet
> server clients also die instead of failing-over to another zookeeper. If
> the clients on the failed zookeeper are only tablet servers, Accumulo
> reassigns the tablets. If the Accumulo Master is one of the clients on the
> failed node, then the master goes down and the cluster with it.****
>
> ** **
>
> Anyone else have this problem or know of a workaround/solution to keep the
> cluster up when zookeeper changes state?****
>
> ** **
>
> Thanks,****
>
> Drew**
>
> ** **
>
> ** **
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB