You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Benjamin Reed (JIRA)" <ji...@apache.org> on 2009/06/04 19:29:07 UTC
[jira] Commented: (ZOOKEEPER-396) race condition in zookeeper
client library between zookeeper_close and zoo_synchronous api
[ https://issues.apache.org/jira/browse/ZOOKEEPER-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716331#action_12716331 ]
Benjamin Reed commented on ZOOKEEPER-396:
-----------------------------------------
+1 looks good.
> race condition in zookeeper client library between zookeeper_close and zoo_synchronous api
> ------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-396
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-396
> Project: Zookeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.1.1
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Critical
> Fix For: 3.2.0
>
> Attachments: test.c, ZOOKEEPER-396.patch
>
>
> There is a race condition in zoopkeeper client library wherein if the application calls zookeeper_close() and zoo_anysynchronouscall simultaneously, sometimes the zoo_sync api call gets hung waiting for a notification whcih will never come.
> We might want to create another bugfix release for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.