You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2020/01/07 02:23:00 UTC

[jira] [Created] (ZOOKEEPER-3675) Clean Up committedLog Interaction in ZKDatabase

David Mollitor created ZOOKEEPER-3675:
-----------------------------------------

             Summary: Clean Up committedLog Interaction in ZKDatabase
                 Key: ZOOKEEPER-3675
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3675
             Project: ZooKeeper
          Issue Type: Improvement
            Reporter: David Mollitor
            Assignee: David Mollitor


* To be proper, minCommittedLog/maxCommittedLog should only be modified in a lock.
 * maxCommittedLog is potentially set twice (to the same value) for each call to the method
 * Streamline code in addCommittedProposal
 * Pre-initialize committedLog data structure to the full size
 * Remove unused commitLogBuffer
 * Remove synchronization of method getCommittedLog(), it is protected with lock
 * Unify grabbing locks outside of try block



--
This message was sent by Atlassian Jira
(v8.3.4#803005)