All,
I'm working on a ZK deployment that will support a heterogeneous set of
processes connecting to the ZK and creating ephemeral nodes. We have the
conflicting requirements that:
a) If a process crashes (closes its socket) without calling a proper
close, we would like the ephemeral node
:
That doesn't sound right to me.
Is there a Zookeeper expert in the house?
On Tue, Aug 31, 2010 at 8:58 AM, Fournier, Camille F. [Tech]
camille.fourn...@gs.com wrote:
I foolishly did not investigate the ZK code closely enough and it seems
that closing the socket still waits
the ephemeral nodes.
ben
On 08/31/2010 01:41 PM, Fournier, Camille F. [Tech] wrote:
Yes that's right. Which network issues can cause the socket to close
without the initiating process closing the socket? In my limited
experience in this area network issues were more prone to leave
?
A new message to the leader to describe connection loss?
On Wed, Sep 8, 2010 at 1:03 PM, Benjamin Reed br...@yahoo-inc.com wrote:
unfortunately, that only works on the standalone server.
ben
On 09/08/2010 12:52 PM, Fournier, Camille F. [Tech] wrote:
This would be the ideal solution
) server gets a reset from client
at step 6 i don't think you want to delete the ephemeral nodes.
ben
On 08/31/2010 01:41 PM, Fournier, Camille F. [Tech] wrote:
Yes that's right. Which network issues can cause the socket to close
without the initiating process closing
To: Fournier, Camille F. [Tech]
Cc: 'zookeeper-user@hadoop.apache.org'
Subject: Re: closing session on socket close vs waiting for timeout
the problem is that followers don't track session timeouts. they track
when they last heard from the sessions that are connected to them
That would be incredibly useful, I keep meaning to just take the code I need
for integration testing from the zk test source but it would be much nicer as a
released jar. I created ZOOKEEPER-903 to track this:
https://issues.apache.org/jira/browse/ZOOKEEPER-903
C
-Original Message-
The ZK documentation says:
New in 3.2: Enables a ZooKeeper ensemble administrator to access the znode
hierarchy as a super user. In particular no ACL checking occurs for a user
authenticated as super.
However, in some testing today I created a digest user, logged in as this user,
set the ACLs
...@apache.org]
Sent: Wednesday, October 20, 2010 2:08 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: Digest user ACL check failing
Sounds like it might be a bug, was this just for the root or for any znode?
Please file a JIRA, thanks.
Patrick
On Tue, Oct 19, 2010 at 1:01 PM, Fournier, Camille F
We have been discussing various implementation options for doing this, but
right now this is not possible. If you are interested in this problem take a
look at https://issues.apache.org/jira/browse/ZOOKEEPER-922, which is one
proposed solution.
C
-Original Message-
From: Steve Gury
Can you clarify what you mean when you say 10-100K watchers? Do you mean
10-100K clients with 1 active watch, or some lesser number of clients with more
watches, or a few clients doing a lot of watches and other clients doing other
things?
-Original Message-
From: Jeremy Hanna
This is exactly the scenario that you use to test session expiration, make one
connection to a ZK and then another with the same session and password, and
close the second connection, which causes the first to expire. It is only a
clean close that will cause this to happen, though (one where
On Thu, Nov 18, 2010 at 9:44 AM, Fournier, Camille F. [Tech]
camille.fourn...@gs.com wrote:
Can you clarify what you mean when you say 10-100K watchers? Do you mean
10-100K clients with 1 active watch, or some lesser number of clients with
more watches, or a few clients doing a lot of watches
13 matches
Mail list logo
