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

Posted to dev@zookeeper.apache.org by "JiangJiafu (JIRA)" <ji...@apache.org> on 2017/05/17 02:09:04 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16013402#comment-16013402 ] 

JiangJiafu commented on ZOOKEEPER-1167:
---------------------------------------

I have read all the comments above, but I don't get the point. 
In what kind of scenarios will this BUG cause a problem? It seems like this bug is not going to be fixed in 3.4.X version, why?

> 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
>             Fix For: 3.5.4, 3.6.0
>
>         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
(v6.3.15#6346)