[
https://issues.apache.org/jira/browse/HBASE-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237697#comment-13237697
]
stack commented on HBASE-4393:
------------------------------
I wrote a note to suggest this NOT be added to 0.94 because its only basic and
its apart from hbase so we shouldn't have to hold up hbase to get it in. Was
also going to talk about this tool being too basic -- emissions are on stdout
only rather than up in jmx, formatted as json or whatever -- but then I thought
we have to start somewhere. We can add to this basic tool later.
The class needs a license and a class comment.
Should be called Canary rather than HBaseCanary.
Put it into a package. Would suggest we start a tool package so o.a.h.h.tool.
Should implement Tool and be run using ToolRunner. Tool adds a little useful
util.
Needs usage as per lars.
Could be added to bin/hbase as 'canary' -- could start/stop it like we
start/stop region. If you do this, then things like log name and location will
be set up for you as it is for rest server and thrift server etc.
Should output be via LOG rather than stdout? Then we can hook its output up
variously.
Skip formatting in the output...the ' - Region ..' i.e. remove the ' - ' prefix.
I think make the few small changes above and we'd have a good start. Thanks
lads. Good stuff
> Implement a canary monitoring program
> -------------------------------------
>
> Key: HBASE-4393
> URL: https://issues.apache.org/jira/browse/HBASE-4393
> Project: HBase
> Issue Type: New Feature
> Components: monitoring
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Assignee: Amandeep Khurana
> Fix For: 0.94.0
>
> Attachments: HBaseCanary.java
>
>
> This JIRA is to implement a standalone program that can be used to do "canary
> monitoring" of a running HBase cluster. This program would gather a list of
> the regions in the cluster, then iterate over them doing lightweight
> operations (eg short scans) to provide metrics about latency as well as alert
> on availability issues.
--
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
