[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-tabpanel&focusedCommentId=12616603#action_12616603 ] james strachan commented on ZOOKEEPER-78: - {quote} Let's stick with

[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-tabpanel&focusedCommentId=12616580#action_12616580 ] james strachan commented on ZOOKEEPER-83: - Hudson does support Maven and

[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-tabpanel&focusedCommentId=12616579#action_12616579 ] james strachan commented on ZOOKEEPER-78: - Wow I confess to be being k

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

[ https://issues.apache.org/jira/browse/ZOOKEEPER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-58: Status: Patch Available (was: Open) just marking this issue as having a patch - does a

[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-tabpanel&focusedCommentId=12616518#action_12616518 ] james strachan commented on ZOOKEEPER-74: - its a very minor thing, but

[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 pat

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12616456#action_12616456 ] james strachan commented on ZOOKEEPER-90: - I guess the earlier we can noti

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12616455#action_12616455 ] james strachan commented on ZOOKEEPER-90: - FWIW I don't

[jira] Created: (ZOOKEEPER-92) spring factory beans for ZooKeeper, ZooKeeperFacade and ZooKeeperServer

Issue Type: Sub-task Components: java client Reporter: james strachan for folks who use Spring for Dependency Injection it might be handy to have a couple of factory beans to make it easier to create and configure the ZooKeeper, ZooKeeperFacade and ZooKeeperServer via the

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

[ https://issues.apache.org/jira/browse/ZOOKEEPER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved ZOOKEEPER-89. - Resolution: Fixed fixed now with [this patch|http://svn.apache.org/viewvc?rev=679354

[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-tabpanel&focusedCommentId=12616446#action_12616446 ] james strachan commented on ZOOKEEPER-78: - Benjamin I added ZOOKEEPER-89

[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()

() - Key: ZOOKEEPER-91 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-91 Project: Zookeeper Issue Type: Sub-task Components: java client Reporter: james strachan Most clients probably wont need this

[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 patch|http://svn.apache.org/viewvc?rev

[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-tabpanel&focusedCommentId=12616426#action_12616426 ] james strachan commented on ZOOKEEPER-63: - So this patch does not attempt to

[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-tabpanel&focusedCommentId=12616420#action_12616420 ] james strachan commented on ZOOKEEPER-84: - BTW here is the code

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

-90 Project: Zookeeper Issue Type: Sub-task Reporter: james strachan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

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

Type: Sub-task Reporter: james strachan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

[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-tabpanel&focusedCommentId=12616418#action_12616418 ] james strachan commented on ZOOKEEPER-22: - BTW you can see the code

[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-tabpanel&focusedCommentId=12616416#action_12616416 ] james strachan commented on ZOOKEEPER-78: - Just added the WhenOwnerList

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

Reporter: james strachan we should implement the [java.util.concurrent.locks.Lock|http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/locks/Lock.html] to make it easier for folks to reuse the Lock and to help make the API be more natural to end users -- This message is

[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-tabpanel&focusedCommentId=12616413#action_12616413 ] james strachan commented on ZOOKEEPER-78: - Thanks for the great comm

[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-tabpanel&focusedCommentId=12616391#action_12616391 ] james strachan commented on ZOOKEEPER-78: - h3. Moving patches for this issu

[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-tabpanel&focusedCommentId=12616374#action_12616374 ] james strachan commented on ZOOKEEPER-22: - BTW this discussion came up rece

[jira] Commented: (ZOOKEEPER-86) intermittent test failure of org.apache.zookeeper.test.AsyncTest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616365#action_12616365 ] james strachan commented on ZOOKEEPER-86: - BTW I have sometimes still seen

[jira] Updated: (ZOOKEEPER-86) intermittent test failure of org.apache.zookeeper.test.AsyncTest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-86: Attachment: patch_for_ZOOKEEPER-86.patch this patch seems to fix the test case on OS X

Re: do the test cases work for anyone else?

Here's the first issue with a patch... https://issues.apache.org/jira/browse/ZOOKEEPER-86 2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>: > It's important to capture this type of information in jira. > > James Strachan wrote: >> >> FWIW I've ran the tests a

[jira] Updated: (ZOOKEEPER-86) intermittent test failure of org.apache.zookeeper.test.AsyncTest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-86: Status: Patch Available (was: Open) about to attach > intermittent test failure

Re: Mailing lists archived on nabble.

Awesome :) 2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>: > Both the user and dev lists are now being archived on nabble. > > http://n2.nabble.com/zookeeper-dev-f578911.html > http://n2.nabble.com/zookeeper-user-f578899.html > > Patrick > -- James --- http://macstrac.blogspot.com/ Open Sourc

Re: Website

2008/7/23 Doug Cutting <[EMAIL PROTECTED]>: > James Strachan wrote: >> >> Tools like wikis are personal things; and folks tend to prefer to use >> the tool they know. > > That's a key point. > > To make a switch you'd need: > 1. Someone familiar

[jira] Updated: (ZOOKEEPER-86) intermittent test failure of org.apache.zookeeper.test.AsyncTest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-86: Attachment: TEST-org.apache.zookeeper.test.AsyncTest.txt here's the output when r

[jira] Created: (ZOOKEEPER-86) intermittent test failure of org.apache.zookeeper.test.AsyncTest

Components: tests Environment: OS X and linux. It sometimes passes; but mostly seems to fail on OS X each time Reporter: james strachan Will attach the test output in an attachment... -- This message is automatically generated by JIRA. - You can reply to this email

Re: assigning JIRAs to non committers

Cool thanks for the heads up! You live and learn :) Its funny how totally different all the various Apache projects are and how they get things done. My bad for not reading the contributing section of the wiki yet :) 2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>: > James Strachan wrote: &

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

[ https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-63: Status: Patch Available (was: Open) about to attach a patch > Race condition in cli

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

[ https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated ZOOKEEPER-63: Attachment: patch_ZOOKEEPER-63.patch This patch avoids the close() method blocking

[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-tabpanel&focusedCommentId=12616151#action_12616151 ] james strachan commented on ZOOKEEPER-63: - BTW here's the hang I seem t

[jira] Created: (ZOOKEEPER-85) register the ZooKeeper mailing lists with nabble.com

: james strachan Assignee: Patrick Hunt Many apache projects including Hadoop register with nabble to host online forums & great online archives of the mailing lists... http://www.nabble.com/Hadoop-f17066.html Currently there's hadoop-core, hbase and lucene on there. I often

Re: mailing lists archived on nabble.com?

Done https://issues.apache.org/jira/browse/ZOOKEEPER-85 2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>: > Good idea. Please enter a Jira and assign it to me. > > Patrick > > > James Strachan wrote: >> >> Many apache projects including Hadoop register with nab

[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-tabpanel&focusedCommentId=12616149#action_12616149 ] james strachan commented on ZOOKEEPER-83: - So long as dependencies don'

[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-tabpanel&focusedCommentId=12616144#action_12616144 ] james strachan commented on ZOOKEEPER-84: - If ZOOKEEPER-78 ever gets commi

assigning JIRAs to non committers

Just an idle observation as I'd never seen this workflow before on JIRA so thought I'd ask :) I've been watching some of the recent JIRA activity with interest. I've seen a few JIRAs arrive, someone submits a test case who's not a committer, then the issue gets assigned to the person who submitted

Re: do the test cases work for anyone else?

FWIW I've ran the tests a few times; I think all these 4 tests have timing failures in them. I've seen all of them fail on OS X at some point. Sometimes only 2 will fail. On Linux I've seen just ClientTest fail. 2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>: > I'm on ubuntu (hardy heron) and they wo

[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-tabpanel&focusedCommentId=12616136#action_12616136 ] james strachan commented on ZOOKEEPER-63: - I wonder if I've seen thi

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Assignee: (was: james strachan) Status: Patch Available (was: Open) Patch is

do the test cases work for anyone else?

I've always had some tests failing on most boxes I try; I wasn't sure if everyone else got those or if they do work on some platforms? On OS X I get these failures [junit] Test org.apache.zookeeper.test.AsyncTest FAILED [junit] Test org.apache.zookeeper.test.WatcherFuncTest FAILED On a li

Re: when should a SessionExpiredException occur?

2008/7/23 James Strachan <[EMAIL PROTECTED]>: > 2008/7/23 Benjamin Reed <[EMAIL PROTECTED]>: >> SessionExpiredExceptions should be extremely rare. Basically they should only >> happen if a machine goes down (of course that would mean no exception would >> actually

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: using_zookeeper_facade.patch This patch no longer requires ZOOKEEPER-84, we

[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-tabpanel&focusedCommentId=12616114#action_12616114 ] james strachan commented on ZOOKEEPER-84: - You can mark this issue as RESO

Re: when should a SessionExpiredException occur?

2008/7/23 Benjamin Reed <[EMAIL PROTECTED]>: > 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

[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-tabpanel&focusedCommentId=12616065#action_12616065 ] james strachan commented on ZOOKEEPER-84: - I hear you :) So an Elect Leade

Re: things lock up when the client reconnects?

ike this? 2008/7/23 James Strachan <[EMAIL PROTECTED]>: > 2008/7/22 Flavio Junqueira <[EMAIL PROTECTED]>: >> James, I'd like to clarify what exactly is the issue you're looking at. If >> you provide a list of ZooKeeper servers, then a client will try to reco

[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-tabpanel&focusedCommentId=12616012#action_12616012 ] james strachan commented on ZOOKEEPER-84: - the ZooKeeper will reconnec

when should a SessionExpiredException occur?

Am just wondering if I've hit this due to some other bug. I thought ZK did keep-alive pings to ensure each client is alive and its session does not expire? Or does the client have to explicitly keep calling some method on the ZooKeeper interface to ensure a steady flow of packets to the ZK server t

mailing lists archived on nabble.com?

Many apache projects including Hadoop register with nabble to host online forums & great online archives of the mailing lists... http://www.nabble.com/Hadoop-f17066.html Currently there's hadoop-core, hbase and lucene on there. I often refer to mailing list posts by nabble link; they're really han

Re: things lock up when the client reconnects?

2008/7/22 Flavio Junqueira <[EMAIL PROTECTED]>: > James, I'd like to clarify what exactly is the issue you're looking at. If > you provide a list of ZooKeeper servers, then a client will try to reconnect > to another ZooKeeper server upon a disconnection. Reconnecting to another > server does not g

[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-tabpanel&focusedCommentId=12615957#action_12615957 ] james strachan commented on ZOOKEEPER-84: - I'm kinda confused by th

Re: Website

2008/7/22 Hiram Chirino <[EMAIL PROTECTED]>: > Lol.. Apache infrastructure supports multiple wiki backends. It's up > to the project to pick which one you want to you. You currently have > picked MoinMoin, but you could have easily picked Confluence, just > like these other Apache projects did: >

[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-tabpanel&focusedCommentId=12615954#action_12615954 ] james strachan commented on ZOOKEEPER-83: - Note its pretty trivial to main

things lock up when the client reconnects?

I wonder if anyone else has seen this recently; I've been trying to make the WriteLock implementation survive server restarts (i.e. reconnecting to another ZK server) with some success. See the latest patch here... https://issues.apache.org/jira/browse/ZOOKEEPER-78 but I've found I can reliably ge

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: patch_with_including_Benjamin's_fix.patch this modified patch includ

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: (was: writeLock_protocol_version3.patch) > added a high level proto

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-84: Attachment: reconnect_patch.patch sorry I forgot to add the patch before :) here it is

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-84: Status: Patch Available (was: Open) about to submit a match - whoops forgot to add it

Re: auto-reconnection ZooKeeper proxy?

ng the cnxn object at least is lowest risk and a simple patch :) and the code should only be executed rarely so performance isn't such an issue. Thoughts? 2008/7/18 James Strachan <[EMAIL PROTECTED]>: > > I work on the ActiveMQ project which implements the JMS API - which is &g

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

Project: Zookeeper Issue Type: Improvement Components: java client Reporter: james strachan am about to attach a patch which adds a reconnect() method to easily re-establish a connection if a session expires - along with a toString() implementation for

[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-tabpanel&focusedCommentId=12615618#action_12615618 ] james strachan commented on ZOOKEEPER-78: - Great catch Benjamin! I've

[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-tabpanel&focusedCommentId=12615546#action_12615546 ] james strachan commented on ZOOKEEPER-83: - I just took a look at the p

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

o 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 thing I would add is

auto-reconnection ZooKeeper proxy?

I work on the ActiveMQ project which implements the JMS API - which is a kinda complex thing but it involves a number of objects (Connections, Sessions, Producers, Consumers). In some JMS providers its the end users responsibility to deal with detecting a connection failure (from any other kind of

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

+1 :) I'm a fellow ActiveMQ hacker too and would love to see ZK included with ActiveMQ. Dependency Injection can really help keep your code simple but leaving it flexible so it can be used in many different ways. Here's some links on DI http://martinfowler.com/articles/injection.html http://www.t

[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-tabpanel&focusedCommentId=12614748#action_12614748 ] james strachan commented on ZOOKEEPER-78: - BTW I just deleted the oth

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: writeLock_protocol_version3.patch Here is an improved version. * we use

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: (was: writeLock_protocol_with_documentation-version2.patch) > adde

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: (was: writeLock_protocol.patch) > added a high level protocol/feat

Re: javadoc for the Write Lock / Leader Election

Thanks for the clarification. I think it makes lots of sense for the leader to write to some canonical place to advertise itself; if others are interested in knowing if it is the leader 2008/7/18 Flavio Junqueira <[EMAIL PROTECTED]>: > Hi James, the fact that the client's node has another node n a

javadoc for the Write Lock / Leader Election

The other thread was already quite big and covering a large range of issues so thought I'd spin up a little separate thread :) I've just updated the patch to include better javadoc which is linked to an embedded HTML documentation describing the protocol. The documention includes the pseudocode fr

javadoc for the Write Lock / Leader Election

The other thread was already quite big and covering a large range of issues so thought I'd spin up a little separate thread :) I've just updated the patch to include better javadoc which is linked to an embedded HTML documentation describing the protocol. The documention includes the pseudocode fr

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: writeLock_protocol_with_documentation-version2.patch here's an updated

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

2008/7/17 Benjamin Reed <[EMAIL PROTECTED]>: > Excellent proposal. The only thing I would add is that there should be > an english description of the recipe in subversion. That way if someone > wanted to do a compatible binding they can do it. If the recipe is on > the wiki it would be hard to keep

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

As a newbie around hadoop/zookeeper (but long time apache hacker on various things), I think the high level protocol/recipe stuff should definitely be a separate, released module; so folks who wanna use it can share a versioned binary and so forth. It would be awesome to have a few good protocols/r

[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-tabpanel&focusedCommentId=12614703#action_12614703 ] james strachan commented on ZOOKEEPER-78: - Thanks Flavio! Totally agreed

[jira] Commented: (ZOOKEEPER-79) Document jacob's leader election on the wiki recipes page

[ https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614448#action_12614448 ] james strachan commented on ZOOKEEPER-79: - Ah cool :) Was just checking we

[jira] Commented: (ZOOKEEPER-79) Document jacob's leader election on the wiki recipes page

[ https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614431#action_12614431 ] james strachan commented on ZOOKEEPER-79: - BTW https://issues.apache.org/

[PATCH] a simple Leader Election or exclusive Write Lock protocol/policy

So having recently discovered ZooKeeper, I'm really liking it - good job folks! I've seen discussions of building high level features from the core ZK library and had not seen any available on the interweb so figured I'd have a try creating a simple one. Feel free to ignore it if a ZK ninja can th

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

-78 Project: Zookeeper Issue Type: New Feature Components: java client Affects Versions: 3.0.0 Reporter: james strachan Attachments: writeLock_protocol.patch Here's a patch which adds a little WriteLock helper class for performing l

[jira] Updated: (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:all-tabpanel ] james strachan updated ZOOKEEPER-78: Attachment: writeLock_protocol.patch > added a high level protocol/feature - for e