[jira] Updated: (ZOOKEEPER-396) race condition in zookeeper client library between zookeeper_close and zoo_synchronous api

2009-06-08 Thread Mahadev konar (JIRA)

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

Mahadev konar updated ZOOKEEPER-396:


  Resolution: Fixed
Hadoop Flags: [Reviewed]
  Status: Resolved  (was: Patch Available)

I just committed this.

 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.



[jira] Updated: (ZOOKEEPER-396) race condition in zookeeper client library between zookeeper_close and zoo_synchronous api

2009-05-29 Thread Mahadev konar (JIRA)

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

Mahadev konar updated ZOOKEEPER-396:


Attachment: ZOOKEEPER-396.patch

after some thinking and digging deep it seems that the problem is occuring 
after we call zookeeper_close and get use the same handle in a seperate thread 
to get data. Similar to FILE api in libc, the behavior of using the handle 
after close is called is undefined and might create problems. So, I have just 
updated the docs in the c code to reflect this in the docs and warn users on 
not doing this.

 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.



[jira] Updated: (ZOOKEEPER-396) race condition in zookeeper client library between zookeeper_close and zoo_synchronous api

2009-05-29 Thread Mahadev konar (JIRA)

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

Mahadev konar updated ZOOKEEPER-396:


Status: Patch Available  (was: Open)

 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.



[jira] Updated: (ZOOKEEPER-396) race condition in zookeeper client library between zookeeper_close and zoo_synchronous api

2009-05-19 Thread Mahadev konar (JIRA)

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

Mahadev konar updated ZOOKEEPER-396:


Fix Version/s: 3.2.0

 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


 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.