[jira] [Created] (ZOOKEEPER-3598) Fix potential data inconsistency issue due to CommitProcessor not gracefully shutdown

["Fangmin Lv (Jira)" <ji...@apache.org>]

Fangmin Lv created ZOOKEEPER-3598:
-------------------------------------

             Summary:  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
             Fix For: 3.6.0


 
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)