You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Raul Gutierrez Segales (JIRA)" <ji...@apache.org> on 2015/06/23 05:51:00 UTC
[jira] [Updated] (ZOOKEEPER-1792) Observers don't need to keep an
in-memory copy of last commited proposals
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Gutierrez Segales updated ZOOKEEPER-1792:
----------------------------------------------
Summary: Observers don't need to keep an in-memory copy of last commited proposals (was: Observers don't need to keep the an in-memory copy of last commited proposals )
> Observers don't need to keep an in-memory copy of last commited proposals
> --------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1792
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1792
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Raul Gutierrez Segales
> Priority: Minor
>
> In FinalRequestProcessor.java#processRequest we have:
> {noformat}
> if (request.isQuorum()) {
> zks.getZKDatabase().addCommittedProposal(request);
> }
> {noformat}
> but this is only useful to the leader since committed proposals are only used from LearnerHandler to sync up followers. I presume followers do need it as they might become a leader at any point. But observers have no need for them, so we could probably special case this for them and optimize the path for them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)