hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Threads leaking from Apache tomcat application
Date Mon, 05 Jan 2015 14:57:41 GMT
I used gmail.

Please consider using third party site where you can upload images.

Cheers

On Mon, Jan 5, 2015 at 6:13 AM, Serega Sheypak <serega.sheypak@gmail.com>
wrote:

> Hi, which mail client you use? I'm using gmail from chrome and see my
> letter with four inlined images.
> There are no links, there are 3 images. I'll reattach them. Maybe the
> problem is in them
>
> 2015-01-05 16:20 GMT+03:00 Ted Yu <yuzhihong@gmail.com>:
>
>> There're several non-English phrases which seem to be links.
>> But when I clicked on them, there was no response.
>>
>> Can you give the links in URL ?
>>
>> Cheers
>>
>>
>>
>> > On Jan 5, 2015, at 2:39 AM, Serega Sheypak <serega.sheypak@gmail.com>
>> wrote:
>> >
>> > Hi, I'm still trying to deal with apache tomcat web-app and hbase HBase
>> 0.98.6
>> > The root problem is that user threads constantly grows. I do get
>> thousands of live threads on tomcat instance. Then it dies of course.
>> >
>> > please see visualVM threads count dynamics
>> >
>> >
>> > Please see selected thread. It should be related to zookeeper (because
>> of thread-name suffix SendThread)
>> >
>> >
>> >
>> > The threaddump for this thread is:
>> >
>> > "visit-thread-27799752116280271-EventThread" - Thread t@75
>> >    java.lang.Thread.State: WAITING
>> >       at sun.misc.Unsafe.park(Native Method)
>> >       - parking to wait for <34671cea> (a
>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>> >       at
>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>> >       at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
>> >       at
>> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
>> >       at
>> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:494)
>> >
>> >    Locked ownable synchronizers:
>> >       - None
>> >
>> > Why does it live "forever"? I next 24 hours I would get ~1200 live
>> theads.
>> >
>> > "visit thread" does simple put/get by key, newrelic says it takes 30-40
>> ms to respond.
>> > I just set a name for the thread inside servlet method.
>> >
>> > Here is CPU profiling result:
>> >
>> >
>> > Here are some Zookeeper metrics.
>> >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message