zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiafu Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ZOOKEEPER-3393) Read-only file system may make the whole ZooKeeper cluster to be unavailable.
Date Tue, 14 May 2019 01:42:00 GMT
Jiafu Jiang created ZOOKEEPER-3393:
--------------------------------------

             Summary: Read-only file system may make the whole ZooKeeper cluster to be unavailable.
                 Key: ZOOKEEPER-3393
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3393
             Project: ZooKeeper
          Issue Type: Bug
          Components: leaderElection, server
    Affects Versions: 3.4.14, 3.4.12
            Reporter: Jiafu Jiang


Say we have 3 nodes: zk1, zk2, and zk3, zk3 is the leader.

If the file system of the ZooKeeper data directory of the leader is read-only due to some
hardware error, the leader will exit and begin a new election.

But the election will keep looping because the new leader may be zk3 again, but zk3 will fail
to write epoch to disk due to read-only file system.

 

Since we have 3 nodes, if only one of them is in problem, should the ZooKeeper cluster be
available? If the answer is yes, then we ought to fix this problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message