zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetić <otis.gospodne...@gmail.com>
Subject Re: acceptedEpoch and currentEpoch values not matching exception message
Date Tue, 22 Sep 2015 14:41:21 GMT
For posterity:

We removed both files, restarted this ZK instance, and ZK recovered.
Never figured out where "10" and "f" were from.

I think this is ZK 3.4.5, but I didn't check.

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/


On Tue, Sep 22, 2015 at 12:23 AM, Otis Gospodnetić <
otis.gospodnetic@gmail.com> wrote:

> Hi,
>
> I've got one of these after a ZK restart... and now ZK doesn't want to
> start:
>
> java.io.IOException: The current epoch, 10 is less than the accepted
> epoch, f
>
> cat version-2/acceptedEpoch
> 15
>
> cat version-2/currentEpoch
> 16
>
> Questions:
> * Where does that "10" come from if currentEpoch file shows 16?
> * Where does that "f" come from if acceptedEpoch shoes 15?
> * Can I manually edit files and fix up numbers? (once I figure out which
> files to edit)
>
> Thanks,
> Otis
> --
> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
> Solr & Elasticsearch Support * http://sematext.com/
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message