Mailing-List: contact user-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.apache.org
Received-SPF: pass (nike.apache.org: domain of henrikno@gmail.com designates
 209.85.216.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1389772152.78624.YahooMailNeo@web173101.mail.ir2.yahoo.com>
References: 
 <CAH3vNzP0ro5tVq-j_0wduk_BnHTJWKU3zrQK0x8poJxG3AAaCA@mail.gmail.com>
 <1389772152.78624.YahooMailNeo@web173101.mail.ir2.yahoo.com>
From: Henrik Nordvik <henrikno@gmail.com>
Date: Wed, 15 Jan 2014 10:05:52 +0100
Message-ID: 
 <CAH3vNzNAhAG9Oj4-oLNz9P51sA7zpEi_VYW2pSiceQLHS=zuOA@mail.gmail.com>
Subject: Re: ConnectionLossException logs a lot on retry
To: user@curator.apache.org,
	=?ISO-8859-1?Q?Evaristo_Jos=E9_Camarero?= <evaristo.camarero@yahoo.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Error is the highest logging level for slf4j, so by setting it to
Fatal effectively disables logging for that class.

I also see the "curator-dont-log-connection-problems" system property
I can set to disable this error (and some other) specifically.

Is this the right way of handling it? Is this hiding an underlying issue?

--
Henrik Nordvik


On Wed, Jan 15, 2014 at 8:49 AM, Evaristo Jos=E9 Camarero
<evaristo.camarero@yahoo.es> wrote:
> Hi there,
>
> I have seen this behaviour in Curator 2.3.0 when ZK ensemble is down and =
at
> least this was not happening with Curator 2.1.0. I am not really sure if
> this is software bug.
>
> Curator relies on slf4j , so the logging configuration can be tune in the
> config file of the logging framwework you are  using.
>
> If you are using log4j and example is using the following line:
> log4j.logger.org.apache.curator =3D FATAL
> but then you will miss all the ERROR information
> You can also use finer grane using:
> log4.logger.o.a.c.f.imps.CuratorFrameworkImpl =3D FATAL
>
> Regards,
>
> Evaristo
>
>
>
> El Martes 14 de enero de 2014 16:20, Henrik Nordvik <henrikno@gmail.com>
> escribi=F3:
> Hi,
> I've hit an issue where I get an error message way too often. This
> message repeats about 10 times every millisecond, which fills our
> disks with logs.
> This happened when zookeeper went down.
>
> 2014-01-14 00:00:04,464 ERROR [mework-0-EventThread]
> o.a.c.f.imps.CuratorFrameworkImpl        - Background operation retry
> gave up
> org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode =3D ConnectionLoss
>         at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> ~[zookeeper-3.4.5.jar:3.4.5-1392090]
>         at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.checkBackgroundRet=
ry(CuratorFrameworkImpl.java:583)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundO=
peration(CuratorFrameworkImpl.java:478)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.curator.framework.imps.DeleteBuilderImpl$2.processResult(Delet=
eBuilderImpl.java:161)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:=
606)
> [zookeeper-3.4.5.jar:3.4.5-1392090]
>         at
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)
> [zookeeper-3.4.5.jar:3.4.5-1392090]
> 2014-01-14 00:00:04,464 ERROR [mework-0-EventThread]
> o.a.c.f.imps.CuratorFrameworkImpl        - Background operation retry
> gave up
> org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode =3D ConnectionLoss
>         at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> ~[zookeeper-3.4.5.jar:3.4.5-1392090]
>         at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.checkBackgroundRet=
ry(CuratorFrameworkImpl.java:583)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundO=
peration(CuratorFrameworkImpl.java:478)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.curator.framework.imps.DeleteBuilderImpl$2.processResult(Delet=
eBuilderImpl.java:161)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:=
606)
> [zookeeper-3.4.5.jar:3.4.5-1392090]
>         at
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)
> [zookeeper-3.4.5.jar:3.4.5-1392090]
> 2014-01-14 00:00:04,465 ERROR [mework-0-EventThread]
> o.a.c.f.imps.CuratorFrameworkImpl        - Background operation retry
> gave up
> org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode =3D ConnectionLoss
>         at
> org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> ~[zookeeper-3.4.5.jar:3.4.5-1392090]
>         at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.checkBackgroundRet=
ry(CuratorFrameworkImpl.java:583)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundO=
peration(CuratorFrameworkImpl.java:478)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.curator.framework.imps.DeleteBuilderImpl$2.processResult(Delet=
eBuilderImpl.java:161)
> [curator-framework-2.3.0.jar:na]
>         at
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:=
606)
> [zookeeper-3.4.5.jar:3.4.5-1392090]
>         at
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)
> [zookeeper-3.4.5.jar:3.4.5-1392090]
>
> Is this an issue with zookeeper or curator?
> How can I configure this so that it's not logging extreme amounts?
>
> --
> Henrik Nordvik
>
>