[
https://issues.apache.org/jira/browse/ZOOKEEPER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661527#comment-13661527
]
Flavio Junqueira commented on ZOOKEEPER-1552:
---------------------------------------------
bq. Not sure how this patch will affect reconfig functionality though, since
Alex mentioned that it is possible to promote an observer to a participant (or
the leader).
The problematic case is participant->observer because the observer with this
patch uses the txn log for committed txns. Consequently, if we convert a
participant to observer and the observer reads the txn log assuming that those
txns have been committed, then it might reach an inconsistent state. But, the
new observer will synchronize with the leader anyway before it starts,
truncating if needed, so it should be fine. We need to make sure that it
happens this way, though.
> Enable sync request processor in Observer
> -----------------------------------------
>
> Key: ZOOKEEPER-1552
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1552
> Project: ZooKeeper
> Issue Type: Improvement
> Components: quorum, server
> Affects Versions: 3.4.3
> Reporter: Thawan Kooburat
> Assignee: Thawan Kooburat
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1552.patch, ZOOKEEPER-1552.patch,
> ZOOKEEPER-1552.patch
>
>
> Observer doesn't forward its txns to SyncRequestProcessor. So it never
> persists the txns onto disk or periodically creates snapshots. This increases
> the start-up time since it will get the entire snapshot if the observer has
> be running for a long time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
