[jira] Commented: (ZOOKEEPER-104) KeptSet: a distributed data stucture backed by the children of a ZooKeeper node

[ https://issues.apache.org/jira/browse/ZOOKEEPER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12618399#action_12618399 ] Benjamin Reed commented on ZOOKEEPER-104: - InterruptedException is something we

[jira] Updated: (ZOOKEEPER-103) Reorganize the ZooKeeper source distro to follow maven conventions

[ https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-103: Status: Open (was: Patch Available) The hierachy implemented by this patch conflicts

[jira] Assigned: (ZOOKEEPER-32) CRCs for ZooKeeper data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed reassigned ZOOKEEPER-32: -- Assignee: Mahadev konar (was: Benjamin Reed) CRCs for ZooKeeper data

[jira] Assigned: (ZOOKEEPER-38) headers (version+) in log/snap files

[ https://issues.apache.org/jira/browse/ZOOKEEPER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed reassigned ZOOKEEPER-38: -- Assignee: Mahadev konar (was: Benjamin Reed) Mahadev is simplifying the patch

[jira] Commented: (ZOOKEEPER-58) Race condition on ClientCnxn.java

[ https://issues.apache.org/jira/browse/ZOOKEEPER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616998#action_12616998 ] Benjamin Reed commented on ZOOKEEPER-58: +1 Race condition on ClientCnxn.java

[jira] Commented: (ZOOKEEPER-97) The code generators should support an optional output directory

[ https://issues.apache.org/jira/browse/ZOOKEEPER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617000#action_12617000 ] Benjamin Reed commented on ZOOKEEPER-97: One thing to keep in mind

Re: when should a SessionExpiredException occur?

SessionExpiredExceptions should be extremely rare. Basically they should only happen if a machine goes down (of course that would mean no exception would actually get generated since the client is dead :) or a network partition occurs. Having said that we seem to have a bug that cause

[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=12616139#action_12616139 ] Benjamin Reed commented on ZOOKEEPER-83: I completely agreed with the goals you

Re: An interest in increasing the DI'ness of ZooKeeper?

This sounds great. I would suggest opening a Jira to work out the proposal and track the patch. ben Hiram Chirino wrote: Yep, I've looked that the test cases. In short to make that public API more DI friendly, we should: * Decouple the current configuration system from the public API. I

Re: Recipe contrib -- was Re: [PATCH] a simple Leader Election or exclusive Write Lock protocol/policy

Some initial implementations of a recipe may only be in C, so it would be nice to have a standard way of finding the recipe that wasn't dependent on the language that implements the recipe. ben James Strachan wrote: 2008/7/17 Benjamin Reed [EMAIL PROTECTED]: Excellent proposal. The only

[jira] Commented: (ZOOKEEPER-38) headers (version+) in log/snap files

[ https://issues.apache.org/jira/browse/ZOOKEEPER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614540#action_12614540 ] Benjamin Reed commented on ZOOKEEPER-38: I really like how you pulled the code

[jira] Resolved: (ZOOKEEPER-47) io thread still around after a EXPIRED_SESSION or AUTH_FAILED event is received

[ https://issues.apache.org/jira/browse/ZOOKEEPER-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed resolved ZOOKEEPER-47. Resolution: Invalid io thread still around after a EXPIRED_SESSION or AUTH_FAILED event

[jira] Created: (ZOOKEEPER-49) SetACL does not work

SetACL does not work Key: ZOOKEEPER-49 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-49 Project: Zookeeper Issue Type: Bug Components: server Reporter: Benjamin Reed As reported by Shane

[jira] Updated: (ZOOKEEPER-48) AUTH_ID not handled correctly when no auth ids are present

[ https://issues.apache.org/jira/browse/ZOOKEEPER-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-48: --- Attachment: acl_3.patch Since the fix for this issue overlaps with ZOOKEEPER-49 and since

[jira] Created: (ZOOKEEPER-46) Clients should check the latencies to the various servers and try to connect to the servers with the lowest latencies first

URL: https://issues.apache.org/jira/browse/ZOOKEEPER-46 Project: Zookeeper Issue Type: Improvement Reporter: Benjamin Reed When ZooKeeper clients and servers are on the same LAN or in the same data center it really doesn't matter which ZooKeeper server

[jira] Commented: (ZOOKEEPER-16) Need to do path validation

[ https://issues.apache.org/jira/browse/ZOOKEEPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605385#action_12605385 ] Benjamin Reed commented on ZOOKEEPER-16: The following characters cannot be used

<    2   3   4   5   6   7