kezhuw opened a new pull request, #2069: URL: https://github.com/apache/zookeeper/pull/2069
Previously, `sync` + `read` could not guarantee up-to-date data as `sync` will not touch quorum in case of no outstanding proposals. Though, `create`/`setData` could be used as an rescue, but it is apparently ugly and error-prone. `sync` fits the semantics naturally. This pr reverts ZOOKEEPER-2137 which using `setData` to circumvent no quorum `sync`. This pr is compatible to our rolling upgrade policy, that is "quorum will be available at all times as long as clients are not starting to use new features". Since `sync` is a public API, so feature gate `quorumSync` is encouraged to be off in rolling upgrade and turn on after rolling upgrade. Refs: ZOOKEEPER-1675, ZOOKEEPER-2136, ZOOKEEPER-3600(#1137) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@zookeeper.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
