[
https://issues.apache.org/jira/browse/ZOOKEEPER-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864988#comment-16864988
]
Enrico Olivelli commented on ZOOKEEPER-2136:
--------------------------------------------
We are going to make a plan for 3.6.0 release.
I don't think this is a real "blocker" issue, in the sense that it is not
mining the stability of ZK, as already said in this thread, sync() is behaving
this way since the beginning.
I think we can change the priority to "Major"
[~phunt] [~fpj] what's your position ?
> Sync() should get quorum acks.
> ------------------------------
>
> Key: ZOOKEEPER-2136
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2136
> Project: ZooKeeper
> Issue Type: Sub-task
> Reporter: Hongchao Deng
> Assignee: Flavio Junqueira
> Priority: Blocker
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2000.patch
>
>
> Currently if the sync packet goes to leader it doesn't get quorum acks. This
> is a problem during reconfig and leader changes. testPortChange() flaky
> failure is caused by such case.
> I proposed to change sync() semantics to require quorum acks in any case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
