You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/07/02 04:32:00 UTC

[jira] [Commented] (HBASE-10147) Canary additions

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

stack commented on HBASE-10147:
-------------------------------

Patch has gone stale (my fault). Code is different now. Unscheduling unless gets picked up for a rebase (still a good idea).... 

> Canary additions
> ----------------
>
>                 Key: HBASE-10147
>                 URL: https://issues.apache.org/jira/browse/HBASE-10147
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: Gustavo Anatoly
>             Fix For: 2.0.0
>
>         Attachments: HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch, HBASE-10147-v2.patch, HBASE-10147-v3.patch, HBASE-10147-v4.patch, HBASE-10147-v5.patch
>
>
> I've been using the canary to quickly identify the dodgy machine in my cluster.  It is useful for this.  What would  make it better would be:
> + Rather than saying how long it took to get a region after you have gotten the region, it'd be sweet to log BEFORE you went to get the region the regionname and the server it is on.  I ask for this because as is, I have to wait for the canary to timeout which can be a while.
> + Second ask is that when I pass the -t, that when it fails, it says what it failed against -- what region and hopefully what server location (might be hard).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)