You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Jacky007 (JIRA)" <ji...@apache.org> on 2013/04/11 14:25:16 UTC

[jira] [Commented] (ZOOKEEPER-1552) Enable sync request processor in Observer

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628877#comment-13628877 ] 

Jacky007 commented on ZOOKEEPER-1552:
-------------------------------------

HI [~thawan], we commit proposal to SyncRequestprocessor, but SyncRequestprocessor may not flush it immediately.
Does we really expect that, throuth it's not a big deal to lose some txns here.
If we should make sure of that, we can make a new processor as the next processor of SyncRequestprocessor to execute "commitProcessor.commit(request)".
Or some comments are help to clarify.
                
> 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