hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Himanshu Vashishtha (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-10563) Set name for FlushHandler thread
Date Tue, 18 Feb 2014 06:21:19 GMT
Himanshu Vashishtha created HBASE-10563:

             Summary: 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

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:
"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)

This message was sent by Atlassian JIRA

View raw message