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
Zookeeper >> mail # user >> Cannot start zookeeper after deleting transaction logs and snapshots


Copy link to this message
-
Re: Cannot start zookeeper after deleting transaction logs and snapshots
Client keeps the last zxid in memory, you just need to restart the client.
By the way, there is a JIRA case on this: ZOOKEEPER-832
On Tue, Nov 12, 2013 at 9:44 AM, ji yan <[EMAIL PROTECTED]> wrote:

> I have made a mistake, in the ignorance of resetting the state of zookeeper
> server, by deleting all the snapshots and transaction logs on the server.
> When I start the server, the log complains
>
> [2013-11-12 00:27:11,201] INFO Refusing session request for client /
> 10.0.1.200:44939 as it has seen zxid 0x79d our last zxid is 0x0 client
> must
> try another server (org.apache.zookeeper.server.NIOServerCnxn)
>
> I understand that this is because the client has kept an offset before and
> it sees that the latest offset in the log ( since all has been removed ) is
> way lower than it last time saw, so it refused to connect to load stale
> data. Can someone tell me how can I get myself unstuck from this situation?
> I cannot find the place where the client keeps the zxid offset.
>
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