hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Ryakhovskiy (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-16142) Trigger JFR session when under duress -- e.g. backed-up request queue count -- and dump the recording to log dir
Date Mon, 11 Jul 2016 07:52:11 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370334#comment-15370334
] 

Konstantin Ryakhovskiy edited comment on HBASE-16142 at 7/11/16 7:52 AM:
-------------------------------------------------------------------------

default JFR tracing added as java-class with main method.
This works when commercial features are enabled.
How should we proceed with testing?
it does not make sense to fail test if commercial features are disabled by default.
from the other perspective, the test should fail, if commercial features are enabled by default,
but not enabled for particular run


was (Author: ryakhovskiy.k):
default JFR tracing added as java-class with main method

> Trigger JFR session when under duress -- e.g. backed-up request queue count -- and dump
the recording to log dir
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-16142
>                 URL: https://issues.apache.org/jira/browse/HBASE-16142
>             Project: HBase
>          Issue Type: Task
>          Components: Operability
>            Reporter: stack
>            Assignee: Konstantin Ryakhovskiy
>            Priority: Minor
>              Labels: beginner
>         Attachments: HBASE-16142.master.001.patch
>
>
> Chatting today w/ a mighty hbase operator on how to figure what is happening during transitory
latency spike or any other transitory 'weirdness' in a server, the idea came up that a java
flight recording during a spike would include a pretty good picture of what is going on during
the time of duress (more ideal would be a trace of the explicit slow queries showing call
stack with timings dumped to a sink for later review; i.e. trigger an htrace when a query
is slow...).
> Taking a look, programmatically triggering a JFR recording seems doable, if awkward (MBean
invocations). There is even a means of specifying 'triggers' based off any published mbean
emission -- e.g. a query queue count threshold -- which looks nice. See https://community.oracle.com/thread/3676275?start=0&tstart=0
and https://docs.oracle.com/javacomponents/jmc-5-4/jfr-runtime-guide/run.htm#JFRUH184
> This feature could start out as a blog post describing how to do it for one server. A
plugin on Canary that looks at mbean values and if over a configured threshold, triggers a
recording remotely could be next. Finally could integrate a couple of triggers that fire when
issue via the trigger mechanism.
> Marking as beginner feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message