[
https://issues.apache.org/jira/browse/HBASE-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548606#comment-13548606
]
takeshi.miao commented on HBASE-4393:
-------------------------------------
There are 4 differences compared with #HBASE-4393
1. this tool will take any one region from each region server to monitor, not
every region in whole HBase cluster
2. this tool was implemented with multi-threaded feature, so it will not be
blocked if any region server being hung
3. this tool is taking one or more region server FQDN as options, then will
monitor the given region servers
3.1 monitor all region servers if no option given
4. this tool can also take one or more regular expression patterns for region
server FQDN for user easily use
I use this tool on our internal HBase operation, so I think that other people
may have the identical requirements
> 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: Matteo Bertozzi
> Fix For: 0.94.0, 0.96.0
>
> Attachments: Canary-v0.java, HBASE-4393-v0.patch, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
