Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 12 Dec 2013 22:49:07 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12684367.1386888515963.27319.1386888547438@arcas>
In-Reply-To: <JIRA.12684367.1386888515963@arcas>
References: <JIRA.12684367.1386888515963@arcas>
Subject: [jira] [Created] (HBASE-10147) Canary additions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

stack created HBASE-10147:
-----------------------------

             Summary: Canary additions
                 Key: HBASE-10147
                 URL: https://issues.apache.org/jira/browse/HBASE-10147
             Project: HBase
          Issue Type: Improvement
            Reporter: stack


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.1.4#6159)