Hi Travis, Do you think it would be possible for you to open a jira and upload your logs?Thanks,-FlavioOn Jul 1, 2010, at 8:13 AM, Travis Crawford wrote:Hey zookeepers -We just experienced a total zookeeper outage, and here's a quickpost-mortem of the issue, and some questions about preventing it g
Hey zookeepers -
We just experienced a total zookeeper outage, and here's a quick
post-mortem of the issue, and some questions about preventing it going
forward. Quick overview of the setup:
- RHEL5 2.6.18 kernel
- Zookeeper 3.3.0
- ulimit raised to 65k files
- 3 cluster members
- 4-5k connection
I think that you are correct, but a real ZK person should answer this.
On Wed, Jun 30, 2010 at 4:48 PM, Bryan Thompson wrote:
> For example, if a client registers a watch, and a state change which would
> trigger that watch occurs _after_ the client has successfuly registered the
> watch with th
Yes. That is true. In particular, your link to a server (or the server
itself) can fail causing your client to switch to a different ZK server and
retry there. This can and often does happen without you knowing.
On Wed, Jun 30, 2010 at 4:48 PM, Bryan Thompson wrote:
> With regard to timelines
Ted,
Yes, that is clear. I was looking for this:
> On some failures (communication errors, timeouts, etc) the client will not
> know if the update has applied or not. We take steps to minimize the
> failures, but the only guarantee is only present with successful return codes.
With regard to
Also this:
Once an update has been applied, it will persist from that time forward
until a client overwrites the update. This guarantee has two corollaries:
If a client gets a successful return code, the update will have been
applied. On some failures (communication errors, timeouts, etc) the clie
On 06/30/2010 09:37 AM, Ted Dunning wrote:
Which API are you talking about? C?
I think that the difference between connection loss and session expiration
might mess you up slightly in your disjunction here.
On Wed, Jun 30, 2010 at 7:45 AM, Bryan Thompson wrote:
I am wondering what guarantee
Ted,
You are correct. This is a resend. The apache mail server had some hiccups
and did not subscribe me until just a few minutes ago and the archives appear
to be out of date so I had no means to verify the delivery of my message, which
I had sent this morning but before having positive conf
Isn't this the same question that you sent this morning?
On Wed, Jun 30, 2010 at 3:36 PM, Bryan Thompson wrote:
> Hello,
>
> I am wondering what guarantees (if any) zookeeper provides for reliable
> messaging for operation return codes up to a session timeout. Basically, I
> would like to know
Hello,
I am wondering what guarantees (if any) zookeeper provides for reliable
messaging for operation return codes up to a session timeout. Basically, I
would like to know whether a zookeeper client can rely on observing the return
code for a successful operation which creates an ephemeral (o
Which API are you talking about? C?
I think that the difference between connection loss and session expiration
might mess you up slightly in your disjunction here.
On Wed, Jun 30, 2010 at 7:45 AM, Bryan Thompson wrote:
> Hello,
>
> I am wondering what guarantees (if any) zookeeper provides for
Hello,
I am wondering what guarantees (if any) zookeeper provides for reliable
messaging for operation return codes up to a session timeout. Basically, I
would like to know whether a zookeeper client can rely on observing the return
code for a successful operation which creates an ephemeral (o
12 matches
Mail list logo
