Return-Path: 
 <user-return-9508-apmail-zookeeper-user-archive=zookeeper.apache.org@zookeeper.apache.org>
X-Original-To: apmail-zookeeper-user-archive@www.apache.org
Delivered-To: apmail-zookeeper-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 89847187F1
	for <apmail-zookeeper-user-archive@www.apache.org>;
 Fri,  6 Nov 2015 20:32:09 +0000 (UTC)
Received: (qmail 62751 invoked by uid 500); 6 Nov 2015 20:32:09 -0000
Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org
Received: (qmail 62696 invoked by uid 500); 6 Nov 2015 20:32:08 -0000
Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@zookeeper.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@zookeeper.apache.org>
List-Post: <mailto:user@zookeeper.apache.org>
List-Id: <user.zookeeper.apache.org>
Reply-To: user@zookeeper.apache.org
Delivered-To: mailing list user@zookeeper.apache.org
Received: (qmail 62620 invoked by uid 99); 6 Nov 2015 20:32:08 -0000
Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2015 20:32:08 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org)
 with ESMTP id 21CC718097F
	for <user@zookeeper.apache.org>; Fri,  6 Nov 2015 20:32:08 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.898
X-Spam-Level: **
X-Spam-Status: No, score=2.898 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001]
	autolearn=disabled
Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=gmail.com
Received: from mx1-us-east.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new,
 port 10024)
	with ESMTP id o674aGVEiHoG for <user@zookeeper.apache.org>;
	Fri,  6 Nov 2015 20:32:07 +0000 (UTC)
Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com
 [209.85.220.176])
	by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with
 ESMTPS id 6144942AB6
	for <user@zookeeper.apache.org>; Fri,  6 Nov 2015 20:32:07 +0000 (UTC)
Received: by qkcn129 with SMTP id n129so50100703qkc.1
        for <user@zookeeper.apache.org>; Fri, 06 Nov 2015 12:32:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=D8V0LtH3R+UvpfFkqY3MPw37DWpf59pFbDflXHrtXg0=;
        b=aOE1Kw1VDzCW6E0Efmi8mErrIJ5rucM/2rwLa0Bag+BhYHdCq3pJM4KzAwvsfp/W8q
         JzBY30dQT9/cJ6RN813klkHf4p1j5gyjc0jvJdsqEQelTiBQMn5olyfIeLCBUb9NPRPP
         Z1iKUzU/P3dOmB1/nQiAWDmIGSAeBepHjzzuUU3dF9Iaqj0BkppUffFMKveKVYdycFH0
         y+MDbCmNzcHT9aleO8fHZSj7RiDrRNjd5tVN7ZLKo+tvzqXf1owSLBfAhtEOV5Xfjop4
         oUZcO8SKnngaCTd/GfBdRkXcVbQNMvy799Ecn+vfWdkfG+ygWDnhl6e2d0Y/V/2sYbTr
         66Ug==
MIME-Version: 1.0
X-Received: by 10.55.75.137 with SMTP id y131mr1973218qka.69.1446841921602;
 Fri, 06 Nov 2015 12:32:01 -0800 (PST)
Received: by 10.140.81.201 with HTTP; Fri, 6 Nov 2015 12:32:01 -0800 (PST)
Date: Fri, 6 Nov 2015 15:32:01 -0500
Message-ID: 
 <CAFau7Xe_u+MoNK+ugWowTCtAz1eyhi0xw+i4YPgdc1uYNYi9Jw@mail.gmail.com>
Subject: out of order callbacks of events in ZK
From: kamel zaarouri <kamel.zaarouri@gmail.com>
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=001a114a9a4ec88b8c0523e522c6

--001a114a9a4ec88b8c0523e522c6
Content-Type: text/plain; charset=UTF-8

Hi zk-users,

Assume this tree:


parent1
|         |____Child1
|
|
parent2
         |_____<empty>


I have 1 watchers on parent1 and another watcher on parent2. I have those
watchers setup to receive updates of the child nodes of both parents.

Child1 is a non-ephemeral node.

If another client:

- Creates an ephemeral node (let's call it ephem2) under parent2
then and only then it
- Updates Child1

What I am seeing now is that 20% of the time, I receive the callbacks out
of order, i.e. I see the Child1 being updated before ephem2 is seen created.

Is this is a bug in the client I am using or does ZK not guarantee order in
this way?

Thank you!,

--001a114a9a4ec88b8c0523e522c6--