hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10147) Canary additions
Date Sun, 02 Jul 2017 04:39:00 GMT

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

Hadoop QA commented on HBASE-10147:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red}
HBASE-10147 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-10147 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12622175/HBASE-10147-v5.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/7450/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Canary additions
> ----------------
>
>                 Key: HBASE-10147
>                 URL: https://issues.apache.org/jira/browse/HBASE-10147
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: Gustavo Anatoly
>         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)

Mime
View raw message