Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 2441 invoked from network); 25 Apr 2010 17:09:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Apr 2010 17:09:47 -0000 Received: (qmail 44229 invoked by uid 500); 25 Apr 2010 17:09:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 44207 invoked by uid 500); 25 Apr 2010 17:09:46 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 44197 invoked by uid 99); 25 Apr 2010 17:09:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Apr 2010 17:09:46 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of beuknight@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Apr 2010 17:09:38 +0000 Received: by wwb24 with SMTP id 24so3006036wwb.31 for ; Sun, 25 Apr 2010 10:09:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=ElTJPlllHIoObyKLDy14BEnxg6idsgvnWqM8S+5bNbY=; b=A2DhWIFIA5i4LwATBmYtSmOjgvnne9WNnRbhCGu/yUt5q1qtWNsTg5lPMhxaXsZETO fM+vKK7amqklwy+9edgHiEFc8rkGbOQprzqRJvkjoOeUvZk+sKo2ZiDI1nNSsVwpffkb idGFerLSfv5yl6v5ezYzkn6xmEiMyHHoaFD40= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=vzwxoIukq/IENNrrHuKURT5520V+Dfjql+47jDwJ+YJ+gcmcDcZtuEG8p1Pz2hRLGM 0VVbz3DG9B4OJ9KMk9DqT6zZET7hHzhQJCr6Rafuph3+isCpjVQnI2uGRsEKb5nuF6fY 1hCd+surtqhHqH87jVSXX/87aTx+aU8iGOKio= MIME-Version: 1.0 Received: by 10.216.89.193 with SMTP id c43mr3916975wef.151.1272215355520; Sun, 25 Apr 2010 10:09:15 -0700 (PDT) Received: by 10.216.47.71 with HTTP; Sun, 25 Apr 2010 10:09:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 26 Apr 2010 00:09:15 +0700 Message-ID: Subject: Re: Cassandra - Thread leak when high concurrent load From: JKnight JKnight To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016e6d46d7d582fec048512b8a1 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d46d7d582fec048512b8a1 Content-Type: text/plain; charset=ISO-8859-1 Thanks Robson, The number of thread gradually increase to 7000. And the server hang up. I know threadpool is used to prevent creating large number of thread. So why Cassandra create large number of thread when high concurrent load. On Sun, Apr 25, 2010 at 5:38 PM, Mark Robson wrote: > > > On 25 April 2010 10:48, JKnight JKnight wrote: > >> Dear all, >> >> My Cassandra server had thread leak when high concurrent load. I used >> jconsole and saw many, many thread occur. >> > > Just because there are a lot of threads, need not imply a thread leak. > Cassandra uses a lot of threads. > > Do you see the number of threads gradually increase during a soak test on > your test cluster? Can you dump the JVM info (I believe sending a signal > makes it dump this)? > > The JMX information viewable via JConsole also gives you a list of threads. > Assuming you see this gradually increasing during the soak test, can you > tellwhich thread pool is increasing? > > Mark > -- Best regards, JKnight --0016e6d46d7d582fec048512b8a1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Robson,

The number of thread gradually increase to 7000. And= the server hang up.
I know threadpool is used to prevent creating larg= e number of thread.

So why Cassandra create large number of thread w= hen high concurrent load.

On Sun, Apr 25, 2010 at 5:38 PM, Mark Robson= <markxr@gmail.com= > wrote:


On 25 April 2010 10:48= , JKnight JKnight <beuknight@gmail.com> wrote:
Dear all,

My Cassandra server had thread leak when high concurrent = load. I used jconsole and saw many, many thread occur.

Just because there are a lot of threads, need not imp= ly a thread leak. Cassandra uses a lot of threads.

Do you see the number of threads gradually increase dur= ing a soak test on your test cluster? Can you dump the JVM info (I believe = sending a signal makes it dump this)?

The JMX info= rmation viewable via JConsole also gives you a list of threads. Assuming yo= u see this gradually increasing during the soak test, can you tellwhich thr= ead pool is increasing?

Mark



--
Best regards,
JKnigh= t
--0016e6d46d7d582fec048512b8a1--