zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2020) Change TRUNC to SNAP in sync phase for safety guarantee
Date Fri, 06 Sep 2019 15:43:12 GMT

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

Enrico Olivelli updated ZOOKEEPER-2020:
---------------------------------------
    Fix Version/s: 3.5.7

> Change TRUNC to SNAP in sync phase for safety guarantee 
> --------------------------------------------------------
>
>                 Key: ZOOKEEPER-2020
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2020
>             Project: ZooKeeper
>          Issue Type: Sub-task
>          Components: quorum
>    Affects Versions: 3.5.0
>            Reporter: Hongchao Deng
>            Priority: Major
>             Fix For: 3.6.0, 3.5.6, 3.5.7
>
>
> ZOOKEEPER-1549 discusses the problem:
> "When the leader started, it will apply every txn in its txnlog (incl. uncommitted ones)
into its in-memory data tree"
> I didn't any solution so far solved this problem in 3.5.x. Since this affects only TRUNC
part -- only old leader that needs TRUNC applies uncommitted txns, a simple fix would be change
current TRUNC logic to SNAP. This isn't hard to implement, but guarantees safety.
> Ideally, we will solve the whole problem by untangling all compatibility issues and fixing
the protocol.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message