Michael Stack created HBASE-23672:
-------------------------------------
Summary: 350+ lossy-count threads running
Key: HBASE-23672
URL: https://issues.apache.org/jira/browse/HBASE-23672
Project: HBase
Issue Type: Bug
Affects Versions: 2.3.0
Reporter: Michael Stack
Looking at a server under load (branch-2), I see 350 instances of lossy-count
threads running. They look like this:
{code}
8611 "lossy-count-0" #11672 daemon prio=5 os_prio=0 cpu=0.09ms elapsed=281.33s
tid=0x00007f1baee76800 nid=0x2411 waiting on condition [0x00007f1b78793000]
8612 java.lang.Thread.State: WAITING (parking)
8613 at jdk.internal.misc.Unsafe.park([email protected]/Native Method)
8614 - parking to wait for <0x00000000910a91e0> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
8615 at
java.util.concurrent.locks.LockSupport.park([email protected]/LockSupport.java:194)
8616 at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await([email protected]/AbstractQueuedSynchronizer.java:2081)
8617 at
java.util.concurrent.LinkedBlockingQueue.take([email protected]/LinkedBlockingQueue.java:433)
8618 at
java.util.concurrent.ThreadPoolExecutor.getTask([email protected]/ThreadPoolExecutor.java:1054)
8619 at
java.util.concurrent.ThreadPoolExecutor.runWorker([email protected]/ThreadPoolExecutor.java:1114)
8620 at
java.util.concurrent.ThreadPoolExecutor$Worker.run([email protected]/ThreadPoolExecutor.java:628)
8621 at java.lang.Thread.run([email protected]/Thread.java:834)
{code}
Why we need 350 threads?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
