hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Dimiduk <ndimi...@gmail.com>
Subject Re: Corrupted log file
Date Wed, 01 May 2013 18:48:05 GMT
Detecting the condition, printing the warning, and breaking the loop sounds
like an urgent bandaid solution to me.


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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message