hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Corrupted log file
Date Sun, 05 May 2013 13:01:30 GMT
Looks like breaking the loop is better choice. 

Cheers

On May 5, 2013, at 4:38 AM, Jean-Marc Spaggiari <jean-marc@spaggiari.org> wrote:

> Ok, I will open a JIRA for that later today...
> 
> On the RS side, should we break the loop? Or kill the server?  Because not
> being able to read the log might end with rs inconsistencies?
> 
> JM
> Le 1 mai 2013 14:51, "Ted Yu" <yuzhihong@gmail.com> a écrit :
> 
>> Ideally HBCK should sideline corrupted log file so that region server can
>> start.
>> 
>> Cheers
>> 
>> On Wed, May 1, 2013 at 11:48 AM, Nick Dimiduk <ndimiduk@gmail.com> wrote:
>> 
>>> 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
>> 

Mime
View raw message