zookeeper-issues 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-3231) Purge task may lost data when the recent snapshots are all invalid
Date Wed, 04 Sep 2019 10:32:00 GMT

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

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

>  Purge task may lost data when the recent snapshots are all invalid
> -------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3231
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3231
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.4, 3.4.13
>            Reporter: Jiafu Jiang
>            Assignee: maoling
>            Priority: Major
>              Labels: pull-request-available
>
> I read the ZooKeeper source code, and I find the purge task use FileTxnSnapLog#findNRecentSnapshots
to find snapshots, but the method does not check whether the snapshots are valid.
> Consider a worse case, a ZooKeeper server may have many invalid snapshots, and when a
purge task begins, it will use the zxid in the last snapshot's name to purge old snapshots
and transaction logs, then we may lost data. 
> I think we should use FileSnap#findNValidSnapshots(int) instead of FileSnap#findNRecentSnapshots
in FileTxnSnapLog#findNRecentSnapshots, but I am not sure.
>  



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

Mime
View raw message