Mahadev konar updated ZOOKEEPER-396:

    Attachment: test.c

here is a simple way to reproduce this. Doing an exists in a loop with some 
other thread closing the zookeeper handle. This test code will hang (sometimes 
in different places). We might want to have a state called closing in the 
client wherein we dont allow other operations to proceed as soon as a close() 
gets called. Also, we need to make sure that the operations that have been 
called before close do not hang. They should atleast get an error response.

> 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
> 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.

Reply via email to