[
https://issues.apache.org/jira/browse/HBASE-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239127#comment-13239127
]
Lars Hofhansl commented on HBASE-5533:
--------------------------------------
While testing a 0.94.0RC I found that this is preventing HBase from shutting
down.
{code}
"decayingSampleTick1" prio=10 tid=0x00007faf5c047000 nid=0x216c waiting on condi
tion [0x00007faf345c1000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000b853e308> (a java.util.concurrent.lock
s.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226
)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject
.awaitNanos(AbstractQueuedSynchronizer.java:2081)
at java.util.concurrent.DelayQueue.take(DelayQueue.java:193)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.tak
e(ScheduledThreadPoolExecutor.java:688)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.tak
e(ScheduledThreadPoolExecutor.java:681)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
{code}
This is the only non-daemon thread I found.
> Add more metrics to HBase
> -------------------------
>
> Key: HBASE-5533
> URL: https://issues.apache.org/jira/browse/HBASE-5533
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.92.2, 0.94.0
> Reporter: Shaneal Manek
> Assignee: Shaneal Manek
> Priority: Minor
> Fix For: 0.94.0, 0.96.0
>
> Attachments: BlockingQueueContention.java, HBASE-5533-0.92-v4.patch,
> HBASE-5533-TRUNK-v6.patch, HBASE-5533-TRUNK-v6.patch, TimingOverhead.java,
> hbase-5533-0.92.patch, hbase5533-0.92-v2.patch, hbase5533-0.92-v3.patch,
> hbase5533-0.92-v5.patch, histogram_web_ui.png
>
>
> To debug/monitor production clusters, there are some more metrics I wish I
> had available.
> In particular:
> - Although the average FS latencies are useful, a 'histogram' of recent
> latencies (90% of reads completed in under 100ms, 99% in under 200ms, etc)
> would be more useful
> - Similar histograms of latencies on common operations (GET, PUT, DELETE)
> would be useful
> - Counting the number of accesses to each region to detect hotspotting
> - Exposing the current number of HLog files
--
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
