Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1761447512.1238414090438.JavaMail.jira@brutus>
Date: Mon, 30 Mar 2009 04:54:50 -0700 (PDT)
From: "Onur GUN (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-7) [hbase] Provide a HBase checker and
 repair tool similar to fsck
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Onur GUN commented on HBASE-7:
------------------------------

Sorry for late reply.

Hi Jim and stack,

Thanks for the replies. Maybe i am thinking of an exceptional or irrelevant situation, i don't know for sure. But let me try to explain.

Lets say that we have run hbasck. It forces flush as it is suggested. Since the base functionality of hbasck is to work in a corruption state; lets say we have corrupt mapfiles, storefiles or regions. I just wonder if there could be a case, that flush triggers some other events or event series "just" because of the corruptions. I mean we reach the split size etc just because of the flush and corruptions.This will not probably effect the results, but i wonder if forcing the flush is the best case. Maybe we should do correction and we should flush later or anything else.  I don't know if this is possible or i am on the correct track, i just need a direction to think of.

I am planning to do this as my SOC by the way. If anybody suggests any other ideas, i will prepare them for my proposal and research to learn more. I will also email Dhruba and try to help if he needs. I think that, i can help testing HADOOP-5189 for now. 

> [hbase] Provide a HBase checker and repair tool similar to fsck
> ---------------------------------------------------------------
>
>                 Key: HBASE-7
>                 URL: https://issues.apache.org/jira/browse/HBASE-7
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: util
>            Reporter: Jim Kellerman
>             Fix For: 0.20.0
>
>         Attachments: patch.txt
>
>
> We need a tool to verify (and repair) HBase much like fsck

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.