You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Enrico Olivelli (Jira)" <ji...@apache.org> on 2019/09/06 15:44:02 UTC

[jira] [Updated] (ZOOKEEPER-1167) C api lacks synchronous version of sync() call.

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enrico Olivelli updated ZOOKEEPER-1167:
---------------------------------------
    Fix Version/s: 3.5.7

> C api lacks synchronous version of sync() call.
> -----------------------------------------------
>
>                 Key: ZOOKEEPER-1167
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1167
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.3.3, 3.4.3, 3.5.0
>            Reporter: Nicholas Harteau
>            Assignee: Marshall McMullen
>            Priority: Major
>             Fix For: 3.6.0, 3.5.6, 3.5.7
>
>         Attachments: ZOOKEEPER-1167.patch
>
>
> Reading through the source, the C API implements zoo_async() which is the zookeeper sync() method implemented in the multithreaded/asynchronous C API.  It doesn't implement anything equivalent in the non-multithreaded API.
> I'm not sure if this was oversight or intentional, but it means that the non-multithreaded API can't guarantee consistent client views on critical reads.
> The zkperl bindings depend on the synchronous, non-multithreaded API so also can't call sync() currently.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)