zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andor Molnar <an...@apache.org>
Subject Re: acceptedEpoch and currentEpoch values not matching exception message
Date Tue, 22 Jan 2019 16:33:44 GMT

Looks there’re a couple of overlapping Jiras around this issue like this:
https://issues.apache.org/jira/browse/ZOOKEEPER-1621 <https://issues.apache.org/jira/browse/ZOOKEEPER-1621>

Mohammad Arshad has provided a patch for ZK-2307 and promised to create a rebased PR. Maybe
you should ping him to do that or create a PR yourself if you feel confidence.

Either way we can fix this for the 3.5 release the earliest.

To workaround the problem I think you should manually update the epoch files to match and
let ZooKeeper start.


> On 2019. Jan 22., at 12:09, hrvoje <hrvoje.djurdjevic@rba.hr> wrote:
> Hi,
> I have zookeeper.version=3.4.10, and I have the same problem, and I see:
> https://issues.apache.org/jira/browse/ZOOKEEPER-2307
> So, this issue is still not resolved, what are my options then? The problem
> appeared due to disk full, and now I cannot start zookeeper.
> --
> Sent from: http://zookeeper-user.578899.n2.nabble.com/

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