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] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing
Date Wed, 18 Jan 2017 05:07:26 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827431#comment-15827431
] 

ASF GitHub Bot commented on ZOOKEEPER-2325:
-------------------------------------------

Github user rakeshadr commented on a diff in the pull request:

    https://github.com/apache/zookeeper/pull/144#discussion_r96568373
  
    --- Diff: src/java/test/org/apache/zookeeper/server/quorum/Zab1_0Test.java ---
    @@ -37,6 +37,8 @@
     import java.util.ArrayList;
     import java.util.HashMap;
     import java.util.List;
    +import java.util.concurrent.ConcurrentHashMap;
    +import java.util.Map;
    --- End diff --
    
    Good catch, @afine. This test is related to ZOOKEEPER-1558. Perhaps, we need to re-look
the fix to see any chance of creating snapshot with uncommitted state.


> 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
>            Priority: Critical
>             Fix For: 3.5.3, 3.6.0
>
>         Attachments: zk.patch, ZOOKEEPER-2325.001.patch, ZOOKEEPER-2325-test.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
(v6.3.4#6332)

Mime
View raw message