Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of VGlushak@luxoft.com
 designates 213.208.171.190 as permitted sender)
From: "Glushak, Vladimir" <VGlushak@luxoft.com>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Subject: HA: High CPU utilization by zookeeper
Thread-Topic: High CPU utilization by zookeeper
Thread-Index: Ac6H5SPAdaVDTzS1TCK7xqWH1/lCAwABQtRqAApyIQAAG6RuVQ==
Date: Wed, 24 Jul 2013 15:30:48 +0000
Message-ID: 
 <DFEDBF0F9F6F61468B464D5C17FBA2D2052812@DB-MBOX-05.dbdc.luxoft.com>
References: 
 <DFEDBF0F9F6F61468B464D5C17FBA2D2052499@DB-MBOX-05.dbdc.luxoft.com>
	<DFEDBF0F9F6F61468B464D5C17FBA2D20524C5@DB-MBOX-05.dbdc.luxoft.com>,<CAB3mbkRS1we7278fK5u-DpOODsHVpjtnpSzbukSXsb4cY86Kaw@mail.gmail.com>
In-Reply-To: 
 <CAB3mbkRS1we7278fK5u-DpOODsHVpjtnpSzbukSXsb4cY86Kaw@mail.gmail.com>
Accept-Language: ru-RU, en-US
Content-Language: ru-RU
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thank you Sergey, maybe that's the reason.

Is it possible to get somewhere zookeeper 3.4.6 snapshot or milestone binar=
ies that includes those patch?

-Vladimir


________________________________________
=EF=D4: Sergey Maslyakov [evolvah@gmail.com]
=EF=D4=D0=D2=C1=D7=CC=C5=CE=CF: 24 =C9=C0=CC=D1 2013 =C7. 9:17
=EB=CF=CD=D5: user@zookeeper.apache.org
=F4=C5=CD=C1: Re: High CPU utilization by zookeeper

I wonder if this has anything to do with the SASL issue in the client:
https://issues.apache.org/jira/browse/ZOOKEEPER-1657


Regards,
/Sergey


On Tue, Jul 23, 2013 at 4:18 PM, Glushak, Vladimir <VGlushak@luxoft.com>wro=
te:

> Hello Zookeeper community,
>
> I've found that our application has issue with high CPU usage.
> I've done some profiling and found out that root cause of this issue is
> thread responsible for connecting to zookeeper.
> After some more investigation, i've found out that my application (one
> process) has few separate sessions (clients ) that connect to zookeeper.
> I've refactored it and decrease number of sessions to 1.
>
> The CPU usage decreased. But still thread responsible for interaction wit=
h
> zoo-server is consuming a lot of resources:
> main-SendThread(zoo.addr:zoo.port)
>         7,044,378.96 [ms]
>         984.896 ms / sec
>
>
> The application is currently in "sleep mode" - it does nothing, but this
> thread is really busy. Should it be such?
> I've found out that this thread is currently works in infinity loop:
> com.db.itrac.router.context.SendThread -> run method, especially  <
> clientCnxnSocket.doTransport(to, pendingQueue, outgoingQueue);  >  consum=
es
> most of resources.
>
>
> To connecting zookeeper I'm using netflix CuratorFramework with default
> configuration. Maybe I'm doing smth wrong, please advice?
>
>
> Also I have two questions:
>
> 1. Should such high CPU consumption thread exists in app? Is it proper
> behavior?
> 2. Can one application has few separate sessions to zookeeper server? Is
> it expected behavior to increase of CPU utilization?
>
>
> ________________________________
>
> This e-mail and any attachment(s) are intended only for the recipient(s)
> named above and others who have been specifically authorized to receive
> them. They may contain confidential information. If you are not the
> intended recipient, please do not read this email or its attachment(s).
> Furthermore, you are hereby notified that any dissemination, distribution
> or copying of this e-mail and any attachment(s) is strictly prohibited. I=
f
> you have received this e-mail in error, please immediately notify the
> sender by replying to this e-mail and then delete this e-mail and any
> attachment(s) or copies thereof from your system. Thank you.
>

________________________________

This e-mail and any attachment(s) are intended only for the recipient(s) na=
med above and others who have been specifically authorized to receive them.=
 They may contain confidential information. If you are not the intended rec=
ipient, please do not read this email or its attachment(s). Furthermore, yo=
u are hereby notified that any dissemination, distribution or copying of th=
is e-mail and any attachment(s) is strictly prohibited. If you have receive=
d this e-mail in error, please immediately notify the sender by replying to=
 this e-mail and then delete this e-mail and any attachment(s) or copies th=
ereof from your system. Thank you.