[
https://issues.apache.org/jira/browse/ZOOKEEPER-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162678#comment-17162678
]
Tharindu commented on ZOOKEEPER-3781:
-------------------------------------
Facing the same issue when upgrading to 3.5.8 from 3.4.14 using the
snapshot.trust.empty=true where some zookeeper nodes in the ensemble did not
have snapshot files.
Having successfully starting up 3.5.8 nodes some of them still had no snapshot
files created and we were not able to start them without the
snapshot.trust.empty=true config.
Had to delete the data and datalog directories and allow syncing from the
ensemble to work around.
> Zookeeper 3.5.7 not creating snapshot
> -------------------------------------
>
> Key: ZOOKEEPER-3781
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3781
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Weichu Liu
> Priority: Major
> Attachments: zk_no_snapshot.zip
>
>
> Hi,
> In our deployment, we are using zookeepers as Kafka quorum.
> Recently we upgraded Zookeeper from 3.4.14 to 3.5.7.
> During the upgrade, we enabled snapshot.trust.empty and removed it after.
> However, about 25% of zookeepers (all on 3.5.7) are not creating snapshot
> files, so they keep crashing on reboot with ERROR.
> {noformat}
> ERROR [main:QuorumPeer@937] - Unable to load database on disk
> <http://java.io|java.io>.IOException: No snapshot found, but there are log
> entries. Something is broken!
> {noformat}
> Nothing suspecious did I find from the zookeeper log.
> I managed to reproduce the issue with the data from our servers, I put them
> in the attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
