[
https://issues.apache.org/jira/browse/ZOOKEEPER-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli resolved ZOOKEEPER-3598.
----------------------------------------
Release Note:
Committed to master branch as 79f99af81842f415b97e1c3c18c953df5bd129b2
(I had a problem with the script and JIRA)
Resolution: Fixed
> Fix potential data inconsistency issue due to CommitProcessor not gracefully
> shutdown
> --------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3598
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3598
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.6.0
> Reporter: Fangmin Lv
> Assignee: Fangmin Lv
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
>
> There was a regression introduced after inline the write in CommitProcessor
> with changes intorduced in ZOOKEEPER-3359, which didn't wait the in-flight
> write to finish before calling shutdown on the nextProcessor.
>
> So it's possible that CommitProcessor thread and QuorumPeer thread will
> update the DataTree concurrently if we're doing fastForwardDataBase at the
> end of ZooKeeperServer.shutdown, which will cause inconsistent issue.
>
> This JIRA is going to make sure we wait on the CommitProcessor to shutdown
> gracefully before calling shutdown on next processor, and exit if we cannot
> finish it gracefully to avoid potential inconsistency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
