zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing
Date Wed, 30 Jan 2019 13:45:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ASF GitHub Bot updated ZOOKEEPER-2325:
--------------------------------------
    Labels: pull-request-available  (was: )

> Data inconsistency if all snapshots empty or missing
> ----------------------------------------------------
>
>                 Key: ZOOKEEPER-2325
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2325
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.6
>            Reporter: Andrew Grasso
>            Assignee: Andrew Grasso
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ZOOKEEPER-2325-test.patch, ZOOKEEPER-2325.001.patch, zk.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When loading state from snapshots on startup, FileTxnSnapLog.java ignores the result
of FileSnap.deserialize, which is -1L if no valid snapshots are found. Recovery proceeds with
dt.lastProcessed == 0, its initial value.
> The result is that Zookeeper will process the transaction logs and then begin serving
requests with a different state than the rest of the ensemble.
> To reproduce:
> In a healthy zookeeper cluster of size >= 3, shut down one node.
> Either delete all snapshots for this node or change all to be empty files.
> Restart the node.
> We believe this can happen organically if a node runs out of disk space.



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

Mime
View raw message