[
https://issues.apache.org/jira/browse/HBASE-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746262#comment-14746262
]
Hadoop QA commented on HBASE-14145:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12756084/testrun2.txt
against master branch at commit 938d2a0c9cfa4c033ccc72de490672f151bb0351.
ATTACHMENT ID: 12756084
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev-support patch that doesn't require tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15608//console
This message is automatically generated.
> Allow the Canary in regionserver mode to try all regions on the server, not
> just one
> ------------------------------------------------------------------------------------
>
> Key: HBASE-14145
> URL: https://issues.apache.org/jira/browse/HBASE-14145
> Project: HBase
> Issue Type: Bug
> Components: canary, util
> Affects Versions: 2.0.0, 1.1.0.1
> Reporter: Elliott Clark
> Assignee: Sanjeev Srivatsa
> Labels: beginner
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-14145-v1.patch, HBASE-14145-v2.patch, testrun.txt,
> testrun2.txt
>
>
> We want a pretty in-depth canary that will try every region on a cluster.
> When doing that for the whole cluster one machine is too slow, so we wanted
> to split it up and have each regionserver run a canary. That works however
> the canary does less work as it just tries one random region.
> Lets add a flag that will allow the canary to try all regions on a
> regionserver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
