Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5777C10471 for ; Tue, 18 Feb 2014 06:50:21 +0000 (UTC) Received: (qmail 861 invoked by uid 500); 18 Feb 2014 06:50:20 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 820 invoked by uid 500); 18 Feb 2014 06:50:19 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 806 invoked by uid 99); 18 Feb 2014 06:50:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Feb 2014 06:50:19 +0000 Date: Tue, 18 Feb 2014 06:50:19 +0000 (UTC) From: "Himanshu Vashishtha (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10563) Set name for FlushHandler thread MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903832#comment-13903832 ] Himanshu Vashishtha commented on HBASE-10563: --------------------------------------------- Yes, 94 also has this issue. I will upload a patch for 94 once hadoop-qa has run/passed (else it will fail trying 94-patch on trunk). > Set name for FlushHandler thread > -------------------------------- > > Key: HBASE-10563 > URL: https://issues.apache.org/jira/browse/HBASE-10563 > Project: HBase > Issue Type: Bug > Components: regionserver > Affects Versions: 0.98.0 > Reporter: Himanshu Vashishtha > Attachments: 10563-v1.patch > > > The FlushHandler thread in MemStoreFlusher class uses default thread name (Thread -XX). This is un-intentional and also confusing in case when there are multiple handlers. > Current Stack trace looks like this: > {code} > "Thread-18" prio=10 tid=0x00007f4e8cb21800 nid=0x356e waiting on condition [0x00007f4e6d49a000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000004e5684b00> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2025) > at java.util.concurrent.DelayQueue.poll(DelayQueue.java:201) > at java.util.concurrent.DelayQueue.poll(DelayQueue.java:39) > at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:228) > at java.lang.Thread.run(Thread.java:662) > {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)