Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of ndimiduk@gmail.com designates
 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPQV63VyurYdFTJqJF8izkhNMVMLwc5amXfKrD8FzQkXaP34PQ@mail.gmail.com>
References: 
 <CAPQV63VyurYdFTJqJF8izkhNMVMLwc5amXfKrD8FzQkXaP34PQ@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Wed, 1 May 2013 11:48:05 -0700
Message-ID: 
 <CANZa=GtjYZizjCGr7L07UStPpnwFrBGev_SwWUN8OuToj7r5WQ@mail.gmail.com>
Subject: Re: Corrupted log file
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7bb0482a2f3ebd04dbac9063

--047d7bb0482a2f3ebd04dbac9063
Content-Type: text/plain; charset=UTF-8

Detecting the condition, printing the warning, and breaking the loop sounds
like an urgent bandaid solution to me.

-n

On Tue, Apr 30, 2013 at 11:51 AM, Jean-Marc Spaggiari <
jean-marc@spaggiari.org> wrote:

> When a log file (into /hbase/.logs) is corrupted, HBase is not able to
> start because it tries to read it again and again.
>
> Also, there is nothing into HBCK to detect that.
>
> Should we have something to check that? Like in hbck, we can simply try to
> open the log file, and read it? To report the warning?
>
> JM
>

--047d7bb0482a2f3ebd04dbac9063--