Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: identifying container nodes
Date: Sun, 18 Dec 2016 12:05:47 -0500
References: <E2C30EF2-48CA-489A-9CD1-5A99FD9FB8EE@yahoo.com>
To: user@zookeeper.apache.org
In-Reply-To: <E2C30EF2-48CA-489A-9CD1-5A99FD9FB8EE@yahoo.com>
Message-Id: <2D58AAD7-9256-4298-9FB1-CDBBFD6FC5F8@jordanzimmerman.com>
archived-at: Sun, 18 Dec 2016 17:06:01 -0000

Sadly, no. There needs to be a new API added to get the metadata for a =
node. When Container (and now TTL) nodes were added we didn=E2=80=99t =
want to break binary compatibility so the metastate is shoehorned into =
the ephemeralOwner value using the high bits. So as not to break =
existing clients those bits are masked away when returning the Stat =
value to clients.

-JZ

> On Dec 18, 2016, at 12:03 PM, Hadriel Kaplan =
<hadrielk@yahoo.com.INVALID> wrote:
>=20
> Howdy,
> Is there some way for us to identify a node as being a Container node, =
distinct from persistent or ephemeral nodes, via a client?
>=20
> Inside of the server, it stores the client's session number in the =
ephemeral owner ID for ephemeral nodes, a value of 0 to identify =
persistent nodes, and a value of CONTAINER_EPHEMERAL_OWNER (a =
Long.MIN_VALUE) to identify Container nodes. But when passing back the =
Stat structure of Container nodes to clients, it uses 0 instead of the =
Long.MIN_VALUE, making it appear as a persistent node to the client. Is =
there some reason for this behavior?
>=20
> It seems easy enough for me to change that behavior for my own use, in =
DataNode.copyStat(), but I'm concerned about making this change if =
there's some good reason it was being faked out.
>=20
> -hadriel
>=20