From user-return-55557-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Fri Sep 28 17:34:18 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4456C180627 for ; Fri, 28 Sep 2018 17:34:18 +0200 (CEST) Received: (qmail 27273 invoked by uid 500); 28 Sep 2018 15:34:16 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 27262 invoked by uid 99); 28 Sep 2018 15:34:16 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2018 15:34:16 +0000 Received: from hw13390.local (pool-96-244-88-135.bltmmd.fios.verizon.net [96.244.88.135]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 1AA70EA8 for ; Fri, 28 Sep 2018 15:34:16 +0000 (UTC) Subject: Re: HConnection in TIMED_WATING To: user@hbase.apache.org References: From: Josh Elser Message-ID: <20bd7bf4-fc72-d1d1-78ca-a778416ded21@apache.org> Date: Fri, 28 Sep 2018 11:34:15 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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* >