Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 14 Oct 2013 16:50:48 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12673725.1381769116875.60720.1381769448285@arcas>
In-Reply-To: <JIRA.12673725.1381769116875@arcas>
References: <JIRA.12673725.1381769116875@arcas>
Subject: [jira] [Commented] (HBASE-9758) Log missing rows and their regions
 if ITBLL fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-9758:
------------------------------

+1 on patch for trunk and 0.96.  I suppose the region could have changed since the fail but this is way better than what we currently have.

> Log missing rows and their regions if ITBLL fails
> -------------------------------------------------
>
>                 Key: HBASE-9758
>                 URL: https://issues.apache.org/jira/browse/HBASE-9758
>             Project: HBase
>          Issue Type: Task
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-9758.patch
>
>
> Currently, when ITBLL fails, the log only shows how many rows are missing. We have to go to the MR log to find the rows. The row key is some binary string that is hard to map to a region.  It will be helpful to log the missing rows in the ITBLL log and the corresponding regions that hold these rows.


--
This message was sent by Atlassian JIRA
(v6.1#6144)