Re: Dynamic adding/removing ZK servers on client

2010-05-03 Thread Dave Wright
seems like it would be required no matter what approach were taken to dynamic clusters. -Dave Wright

Re: Dynamic adding/removing ZK servers on client

2010-05-03 Thread Dave Wright
Well, that just handles distribution of the list (which isn't really our problem), it doesn't help with restarting the ZK client when the list changes - it only pulls the list once, so you still have to completely shutdown and restart the ZK client. Well the old server is being shutdown

Re: Dynamic adding/removing ZK servers on client

2010-05-03 Thread Dave Wright
Yes, that's what I meant - we could update the ZK client lib to do this. It would be invisible to the client application (your code) itself. I don't think that's a bad idea, and the general approach in ZK-146 of using an interface that gets called to retrieve the list of hosts seems good (so

Re: Dynamic adding/removing ZK servers on client

2010-05-03 Thread Dave Wright
Should this be a znode in the privileged namespace? I think having a znode for the current cluster members is part of the ZOOKEEPER-107 proposal, with the idea being that you could get/set the membership just by writing to that node. On the client side, you could watch that znode and update

Re: Dynamic adding/removing ZK servers on client

2010-05-03 Thread Dave Wright
This is tricky: what happens if the server your client is connected to is decommissioned by a view change, and you are unable to locate another server to connect to because other view changes committed while you are reconnecting have removed all the servers you knew about. We'd need to make

build.xml from 3.3.1 distribution has version=3.3.2-dev

2010-09-17 Thread Dave Wright
it appears that the build.xml was modified and bundled up for distribution after the binary was built. Not sure if it's worth fixing in the distribution, but thought I'd at least mention it. -Dave Wright

[jira] Created: (ZOOKEEPER-762) Allow dynamic addition/removal of server nodes in the client API

2010-05-03 Thread Dave Wright (JIRA)
-task Components: c client, java client Reporter: Dave Wright Priority: Minor Currently the list of zookeeper servers needs to be provided to the client APIs at construction time, and cannot be changed without a complete shutdown/restart of the client API

[jira] Commented: (ZOOKEEPER-704) GSoC 2010: Read-Only Mode

2010-05-08 Thread Dave Wright (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12865465#action_12865465 ] Dave Wright commented on ZOOKEEPER-704: --- This is a great idea, but I'm afraid

[jira] Commented: (ZOOKEEPER-885) Zookeeper drops connections under moderate IO load

2010-10-15 Thread Dave Wright (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921459#action_12921459 ] Dave Wright commented on ZOOKEEPER-885: --- I don't think the cause of this is much

[jira] Commented: (ZOOKEEPER-885) Zookeeper drops connections under moderate IO load

2010-10-15 Thread Dave Wright (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921528#action_12921528 ] Dave Wright commented on ZOOKEEPER-885: --- Has it been verified that ZK is doing