[
https://issues.apache.org/jira/browse/HBASE-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144679#comment-13144679
]
Hudson commented on HBASE-4745:
-------------------------------
Integrated in HBase-TRUNK #2412 (See
[https://builds.apache.org/job/HBase-TRUNK/2412/])
HBASE-4745 LRU statistics thread should be a daemon
apurtell :
Files :
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/io/hfile/LruBlockCache.java
> LRU Statistics thread should be daemon
> --------------------------------------
>
> Key: HBASE-4745
> URL: https://issues.apache.org/jira/browse/HBASE-4745
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Andrew Purtell
> Fix For: 0.92.0, 0.94.0
>
> Attachments: HBASE-4745.patch
>
>
> Here was from 'HBase 0.92/Hadoop 0.22 test results' discussion on dev@hbase
> {code}
> "LRU Statistics #0" prio=10 tid=0x00007f4edc7dd800 nid=0x211a waiting
> on condition [0x00007f4e631e2000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00007f4e88acc968> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2025)
> at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> {code}
> We should make this thread daemon thread.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
