[jira] Commented: (ZOOKEEPER-22) Automatic request retries on connect failover

[ https://issues.apache.org/jira/browse/ZOOKEEPER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616374#action_12616374 ] james strachan commented on ZOOKEEPER-22: - BTW this discussion came up recently

[jira] Created: (ZOOKEEPER-88) implement java.util.concurrent.locks.Lock

implement java.util.concurrent.locks.Lock - Key: ZOOKEEPER-88 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-88 Project: Zookeeper Issue Type: Sub-task Components: java client

[jira] Commented: (ZOOKEEPER-78) added a high level protocol/feature - for easy Leader Election or exclusive Write Lock creation

[ https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616416#action_12616416 ] james strachan commented on ZOOKEEPER-78: - Just added the WhenOwnerListener

[jira] Created: (ZOOKEEPER-89) invoke WhenOwnerListener.whenNotOwner() when the ZK connection fails

invoke WhenOwnerListener.whenNotOwner() when the ZK connection fails Key: ZOOKEEPER-89 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-89 Project: Zookeeper Issue

[jira] Created: (ZOOKEEPER-90) invoke WhenOwnerListener.whenNotOwner() when the ZK session expires and the znode is the leader

invoke WhenOwnerListener.whenNotOwner() when the ZK session expires and the znode is the leader --- Key: ZOOKEEPER-90 URL:

[jira] Commented: (ZOOKEEPER-84) provide a mechanism to reconnect a ZooKeeper if a client receives a SessionExpiredException

[ https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616420#action_12616420 ] james strachan commented on ZOOKEEPER-84: - BTW here is the code for

[jira] Commented: (ZOOKEEPER-63) Race condition in client close() operation

[ https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616426#action_12616426 ] james strachan commented on ZOOKEEPER-63: - So this patch does not attempt to fix

[jira] Commented: (ZOOKEEPER-87) Follower does not shut itself down if its too far behind the leader.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616435#action_12616435 ] Flavio Paiva Junqueira commented on ZOOKEEPER-87: - Mahadev, I was

[jira] Resolved: (ZOOKEEPER-90) invoke WhenOwnerListener.whenNotOwner() when the ZK session expires and the znode is the leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved ZOOKEEPER-90. - Resolution: Fixed this is now fixed in [this

Build failed in Hudson: ZooKeeper-trunk #32

See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/32/changes -- [...truncated 17082 lines...] [junit] 2008-07-24 10:41:52,829 - INFO [main:[EMAIL PROTECTED] - Client test setup [junit] 2008-07-24 10:41:57,896 - INFO [main:[EMAIL

[jira] Created: (ZOOKEEPER-91) provide an option for the WriteLock to also watch the locks own znode, so that if someone else deletes it then it is equivalent to calling WriteLock.unlock()

provide an option for the WriteLock to also watch the locks own znode, so that if someone else deletes it then it is equivalent to calling WriteLock.unlock()

[jira] Updated: (ZOOKEEPER-88) implement java.util.concurrent.locks.Lock

[ https://issues.apache.org/jira/browse/ZOOKEEPER-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-88: Status: Patch Available (was: Open) I've just submitted an [initial patch at

[jira] Commented: (ZOOKEEPER-74) Cleaning/restructuring up Zookeeper server code

[ https://issues.apache.org/jira/browse/ZOOKEEPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616518#action_12616518 ] james strachan commented on ZOOKEEPER-74: - its a very minor thing, but the

[jira] Commented: (ZOOKEEPER-83) Switch to using maven to build ZooKeeper

[ https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616583#action_12616583 ] Nigel Daley commented on ZOOKEEPER-83: -- +1 for staying with Ant and creating maven

[jira] Closed: (ZOOKEEPER-39) Use Watcher objects rather than boolean on read operations

[ https://issues.apache.org/jira/browse/ZOOKEEPER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kornev closed ZOOKEEPER-39. -- Use Watcher objects rather than boolean on read operations

[jira] Updated: (ZOOKEEPER-39) Use Watcher objects rather than boolean on read operations

[ https://issues.apache.org/jira/browse/ZOOKEEPER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kornev updated ZOOKEEPER-39: --- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed Use

[jira] Commented: (ZOOKEEPER-74) Cleaning/restructuring up Zookeeper server code

[ https://issues.apache.org/jira/browse/ZOOKEEPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616755#action_12616755 ] Patrick Hunt commented on ZOOKEEPER-74: --- +1 - I always found the field issue james

[jira] Commented: (ZOOKEEPER-74) Cleaning/restructuring up Zookeeper server code

[ https://issues.apache.org/jira/browse/ZOOKEEPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616757#action_12616757 ] Patrick Hunt commented on ZOOKEEPER-74: --- According to the homepage checkstyle

[jira] Commented: (ZOOKEEPER-74) Cleaning/restructuring up Zookeeper server code

[ https://issues.apache.org/jira/browse/ZOOKEEPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616765#action_12616765 ] Patrick Hunt commented on ZOOKEEPER-74: --- We may want to use violations which hadoop