zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 박영근(Alex) <alex.p...@nexr.com>
Subject Re: NodeExistsException when creating a znode with sequential and ephemeral mode
Date Tue, 30 Aug 2011 02:19:59 GMT
We used 3.3.3.

We will check out the latest code.

Thanks Camille.

Alex

2011/8/30 Camille Fournier <camille@apache.org>

> More specifically, we fixed this for the upcoming release:
> https://issues.apache.org/jira/browse/ZOOKEEPER-1046
>
> You can try checking out the latest code and building it, should fix
> your error. I believe 3.3.4 will be released in a week or two.
>
> c
>
> On Mon, Aug 29, 2011 at 9:56 PM, Camille Fournier <camille@apache.org>
> wrote:
> > What version of ZK were you using?
> >
> > On Mon, Aug 29, 2011 at 9:50 PM, 박영근(Alex) <alex.park@nexr.com> wrote:
> >> Hi, all
> >>
> >> I met a problem of NodeExistsException when creating a znode with
> sequential
> >> and ephemeral mode.
> >> the number of total test was 6442314 and 797 errors had occurred.
> >>
> >> The related log message is as in the following:
> >> 2011-08-27 16:26:17,559 - INFO
>  [ProcessThread:-1:PrepRequestProcessor@407][]
> >> - Got user-level KeeperException when processing
> sessionid:0x2320911802a0002
> >> type:create cxid:0x1246d7 zxid:0xfffffffffffffffe txntype:unknown
> >> reqpath:n/a Error
> >> Path:/NexR/MasteElection/__rwLock/readLock-lssm07-0005967078
> >> Error:KeeperErrorCode = NodeExists for
> >> /NexR/MasteElection/__rwLock/readLock-lssm07-0005967078
> >>
> >> The sequential number would be created by increasing parent's Cversion
> in
> >> the PrepRequestProcess.
> >> So, I guess that this problem was caused by inconsistency of parent
> znode.
> >>
> >> Our test scenario is very aggressive:
> >> The grinder agent sends a request of creating a znode of
> >> CreateMode. SEQUENTIAL_EPHEMERAL.
> >> three number of servers compose ensemble.
> >> each NIC of server is down and up repeatedly;
> >> NIC of server1 become down every one minute and sleeping for 9 seconds,
> then
> >> up
> >> NIC of server2 become down every 2 minute and sleeping for 9 seconds,
> then
> >> up
> >> NIC of server3 become down every 3 minute and sleeping for 9 seconds,
> then
> >> up
> >>
> >> while the probability of error occurrence is 0.0001 as mentioned above,
> >> if the ZooKeeper cannot guarantee the consistency, it is  a fatal.
> >>
> >> Is there any idea or related issue?
> >>
> >> thanks in advance.
> >>
> >> alex.
> >>
> >
>

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