zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Rosien <a...@rosien.net>
Subject Re: methods to figure out what causes an ephemeral node to be deleted
Date Fri, 02 Mar 2012 03:47:48 GMT
Well I'm instantiating multiple twitter scala-zookeeper-clients (
https://github.com/twitter/scala-zookeeper-client) which each cons up their
own ZooKeeper instances. I haven't patched their code to accept an existing
ZooKeeper instance to share.

So... by tricky, what do you mean?

On Thu, Mar 1, 2012 at 7:44 PM, Camille Fournier <camille@apache.org> wrote:

> You can do that. All to the same cluster? It can definitely get tricky to
> manage depending on what you're using them for.
>
> On Thu, Mar 1, 2012 at 10:43 PM, Adam Rosien <adam@rosien.net> wrote:
>
> > That got me some info, looks like some sessions expired exactly then:
> >
> > 3/1/12 5:02:44 PM PST session 0x233a2e751981696 cxid 0x0 zxid
> 0x1424f05e44
> > closeSession
> > 3/1/12 5:02:44 PM PST session 0x433a2e7600f15fc cxid 0x0 zxid
> 0x1424f05e45
> > closeSession
> >
> > I'm running multiple ZooKeeper clients in one JVM, that's ok right?
> >
> > On Thu, Mar 1, 2012 at 7:14 PM, Camille Fournier <camille@apache.org>
> > wrote:
> >
> > > Actually, I think for this if you just use the LogFormatter that comes
> > > inside ZooKeeper (zookeeper.server.LogFormatter) you should be able to
> > > find the information you need.
> > >
> > > C
> > > >
> > > > On Thu, Mar 1, 2012 at 9:47 PM, Camille Fournier <camille@apache.org
> >
> > > wrote:
> > > >> Running your transaction logs through the LogFormatter. You should
> see
> > > >> an explicit delete, or the close of the owning session. The
> > > >> LogFormatter is not awesome though... I have some better versions
of
> > > >> it that I will throw up on GitHub in a bit and link if you're
> > > >> interested.
> > > >>
> > > >> On Thu, Mar 1, 2012 at 9:43 PM, Adam Rosien <adam@rosien.net>
> wrote:
> > > >>> I'm trying to track down the exact cause of an ephemeral node
being
> > > >>> deleted. I know it could be either (a) the session where the node
> was
> > > >>> created has expired, or (b) some session, perhaps the same one
that
> > > created
> > > >>> the node, explicitly deletes the node. Is there a good way to
> figure
> > > out,
> > > >>> client-side or server-side, the actual cause of a node deletion?
> > > >>>
> > > >>> Specifically, I have a log message like the following, and I want
> to
> > > know
> > > >>> "where" it came from:
> > > >>>
> > > >>> 2012-03-01 17:02:44 [main-SendThread(blah:2181)] [DEBUG]
> > > >>> [org.apache.zookeeper.ClientCnxn         ] - Got WatchedEvent
> > > >>> state:SyncConnected type:NodeDeleted path:/blah/blah/blah for
> > sessionid
> > > >>> 0x333a2e75199161b
> > > >>>
> > > >>> Also, is the referenced session id the session id of a watch on
the
> > > deleted
> > > >>> node, or the session id of the session that deleted the node?
I'm
> > > guessing
> > > >>> the former.
> > > >>>
> > > >>> .. Adam
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message