cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JKnight JKnight <beukni...@gmail.com>
Subject Re: Cassandra - Thread leak when high concurrent load
Date Sun, 25 Apr 2010 17:09:15 GMT
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 <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 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

Mime
View raw message