hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <els...@apache.org>
Subject Re: HConnection in TIMED_WATING
Date Fri, 28 Sep 2018 15:34:15 GMT
That thread is a part of the ThreadPool that HConnection uses and that 
thread is simply waiting for a task to execute. It's not indicative of 
any problem.

See how the thread is inside of a call to LinkedBlockingQueue#poll()

On 9/28/18 3:02 AM, Lalit Jadhav wrote:
> While load testing in the application, In Thread dump, collected when the
> application was in its highest utilization and found that hconnection was
> in TIMED_WATING (Below log occurred continuously)
> 
> hconnection-0x52cf832d-shared--pool1-t110 - priority:5 -
> threadId:0x00005651030a9800 - nativeId:0x11b - state:TIMED_WAITING
> stackTrace:
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000003f8200ca0> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Locked ownable synchronizers:
> - None--
> 
> Can anyone explain this what's going wrong here?
> 
> Regards,
> *Lalit Jadhav,*
> *Database Group Lead.*
> *Everything happens to everybody sooner or later if there is time enough*
> 

Mime
View raw message