You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Jean-Marc Spaggiari <je...@spaggiari.org> on 2013/04/30 20:51:28 UTC
Corrupted log file
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
Re: Corrupted log file
Posted by Ted Yu <yu...@gmail.com>.
Looks like breaking the loop is better choice.
Cheers
On May 5, 2013, at 4:38 AM, Jean-Marc Spaggiari <je...@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" <yu...@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 <nd...@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
>>
Re: Corrupted log file
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
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" <yu...@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 <nd...@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
> > >
> >
>
Re: Corrupted log file
Posted by Ted Yu <yu...@gmail.com>.
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 <nd...@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
> >
>
Re: Corrupted log file
Posted by Nick Dimiduk <nd...@gmail.com>.
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
>