Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-10563

Set name for FlushHandler thread

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.98.0
    • 0.96.2, 0.98.1, 0.99.0
    • regionserver
    • None

    Description

      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)
      

      Attachments

        1. 10563-v1.patch
          1 kB
          Himanshu Vashishtha

        Activity

          People

            v.himanshu Himanshu Vashishtha
            v.himanshu Himanshu Vashishtha
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: