Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
From: Martin Serrano <martin@attivio.com>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Subject: Re: How to catch NodeExistsException
Thread-Topic: How to catch NodeExistsException
Thread-Index: AQHQ4dspSA/m+sDCpUCuB2hJhwzDHw==
Date: Fri, 28 Aug 2015 22:01:22 +0000
Message-ID: 
 <CY1PR0501MB164453EEDD821B95407B04B3C06E0@CY1PR0501MB1644.namprd05.prod.outlook.com>
References: 
 <CAMjVhWyC3oiDTHcATSJSSb-q357RKXirDhLP46yWiEvH8otf+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: attivio.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Aug 2015 22:01:22.6215
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f2451f17-698f-4d48-b34a-740e2ecaa55e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1644

I find this annoying too.  At one point my company was running a custom=0A=
zookeeper build that turned those messages to DEBUG on the server.  We=0A=
did not want to change the logging level because we found the other INFO=0A=
messages are useful.  The only thing I know to do is to use an existence=0A=
check first but this is unfortunate because it requires two calls. =0A=
Maybe a multi-op could be used but that seems too complex for such a=0A=
common use case.=0A=
=0A=
-Martin=0A=
=0A=
On 08/28/2015 05:47 PM, Daniel Kashtan wrote:=0A=
> I have this code using Curator:=0A=
>=0A=
> try=0A=
> {=0A=
>    client.create().forPath(path);=0A=
> }=0A=
> catch (KeeperException.NodeExistsException ex)=0A=
> {=0A=
>    LOG.debug("caught NodeExistsException");=0A=
> }=0A=
>=0A=
> The trouble is that it is never caught and zookeeper pollutes my producti=
on=0A=
> logs with what are probably harmless exceptions. I assume that my code=0A=
> executes just fine but later on the ZooKeeper server throws the exception=
=0A=
> as it does work in the background. Is there a way to gracefully catch tho=
se=0A=
> exceptions so they don't pile up in my production logs?=0A=
>=0A=
> I have tried in the past to fix my code so these exceptions are never=0A=
> thrown, but I have not found much in the documentation or on google on ho=
w=0A=
> to deal with these exceptions. Is it a known problem? I would love to sol=
ve=0A=
> these issues too if possible.=0A=
>=0A=
=0A=