You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "gaoyu (Jira)" <ji...@apache.org> on 2021/04/15 08:21:00 UTC
[jira] [Created] (ZOOKEEPER-4283) The zookeeper node cannot restart
due an unexpected crash
gaoyu created ZOOKEEPER-4283:
--------------------------------
Summary: The zookeeper node cannot restart due an unexpected crash
Key: ZOOKEEPER-4283
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4283
Project: ZooKeeper
Issue Type: Bug
Affects Versions: 3.6.3
Reporter: gaoyu
I am using the latest stable release 3.6.3. Here is the minimal workload to reproduce the bug:
# There is a zookeeper cluster with three nodes: node1, node2 and node3;
# Start the cluster from scratch;
# node2 becomes the leader;
# Stop node2;
# node3 becomes the new leader;
# Client requests to create a znode;
# Restart node2;
# node2 receives SNAP from node3;
# node2 receives the NEWLEADER message from node3;
# node2 takes current snapshot;
# node2 crashes before writing to the current epoch file;
# Restart node2 but it fails since "Unable to load database on disk".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)