I have issue below when I'm runing hbck:

ERROR: Found lingering reference file
hdfs://node3:9000/hbase/entry_proposed/fbd1735591467005e53f48645278b006/recovered.edits/0000000000091843039.temp

and I'm wondering what it means...

Thanks,

JM

On Mon, Jan 21, 2013 at 12:01 PM, Jean-Marc Spaggiari <
[EMAIL PROTECTED]> wrote:

> Found lingering reference file

The comment on the method that is finding the lingering reference files is
pretty good:
http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#604

It looks like a reference file that lost its referencee.

If you pass this arg., does it help?

http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#3391
St.Ack

Hum. It's still a bit obscur for me how this happend to my cluster...

-repair helped to fix that, so I'm now fine. I will re-run the job I
ran and see if this is happening again.

Thanks,

JM

2013/1/21, Stack <[EMAIL PROTECTED]>:
> On Mon, Jan 21, 2013 at 12:01 PM, Jean-Marc Spaggiari <
> [EMAIL PROTECTED]> wrote:
>
>> Found lingering reference file
>
>
>
> The comment on the method that is finding the lingering reference files is
> pretty good:
> http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#604
>
> It looks like a reference file that lost its referencee.
>
> If you pass this arg., does it help?
>
> http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#3391
>
>
> St.Ack
>

Did you get the name of the broken reference?  I'd trace its life in
namenode logs and in regionserver log by searching its name (You might have
to find the region in master logs to see where region landed over time).
The reference name includes the encoded region name as a suffix.  This is
the region that the reference 'references'.... so need to figure what
happened with it.  Did it get cleaned up before reference was cleared?
 (Something that should not happen).

St.Ack
On Mon, Jan 21, 2013 at 2:20 PM, Jean-Marc Spaggiari <
[EMAIL PROTECTED]> wrote:

> Hum. It's still a bit obscur for me how this happend to my cluster...
>
> -repair helped to fix that, so I'm now fine. I will re-run the job I
> ran and see if this is happening again.
>
> Thanks,
>
> JM
>
> 2013/1/21, Stack <[EMAIL PROTECTED]>:
> > On Mon, Jan 21, 2013 at 12:01 PM, Jean-Marc Spaggiari <
> > [EMAIL PROTECTED]> wrote:
> >
> >> Found lingering reference file
> >
> >
> >
> > The comment on the method that is finding the lingering reference files
> is
> > pretty good:
> >
> http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#604
> >
> > It looks like a reference file that lost its referencee.
> >
> > If you pass this arg., does it help?
> >
> >
> http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#3391
> >
> >
> > St.Ack
> >
>

RECOVERED_EDITS is not a column family.  It should be ignored by hbck.

Filed a jira:

https://issues.apache.org/jira/browse/HBASE-7640

Thanks,
Jimmy

On Mon, Jan 21, 2013 at 2:36 PM, Stack <[EMAIL PROTECTED]> wrote:

> Did you get the name of the broken reference?  I'd trace its life in
> namenode logs and in regionserver log by searching its name (You might have
> to find the region in master logs to see where region landed over time).
> The reference name includes the encoded region name as a suffix.  This is
> the region that the reference 'references'.... so need to figure what
> happened with it.  Did it get cleaned up before reference was cleared?
>  (Something that should not happen).
>
> St.Ack
>
>
> On Mon, Jan 21, 2013 at 2:20 PM, Jean-Marc Spaggiari <
> [EMAIL PROTECTED]> wrote:
>
> > Hum. It's still a bit obscur for me how this happend to my cluster...
> >
> > -repair helped to fix that, so I'm now fine. I will re-run the job I
> > ran and see if this is happening again.
> >
> > Thanks,
> >
> > JM
> >
> > 2013/1/21, Stack <[EMAIL PROTECTED]>:
> > > On Mon, Jan 21, 2013 at 12:01 PM, Jean-Marc Spaggiari <
> > > [EMAIL PROTECTED]> wrote:
> > >
> > >> Found lingering reference file
> > >
> > >
> > >
> > > The comment on the method that is finding the lingering reference files
> > is
> > > pretty good:
> > >
> >
> http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#604
> > >
> > > It looks like a reference file that lost its referencee.
> > >
> > > If you pass this arg., does it help?
> > >
> > >
> >
> http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/HBaseFsck.html#3391
> > >
> > >
> > > St.Ack
> > >
> >
>

On Mon, Jan 21, 2013 at 2:45 PM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:

> RECOVERED_EDITS is not a column family.  It should be ignored by hbck.
>
> Filed a jira:
>
> https://issues.apache.org/jira/browse/HBASE-764<https://issues.apache.org/jira/browse/HBASE-7640>
Thanks Jimmy.  That makes sense now you mention it (smile).
St.Ack

Ok, so basically, there was no issues with my tables? I did not used
any specific keywors for my CF... They are all called "@" or "A" ;)

2013/1/21, Stack <[EMAIL PROTECTED]>:
> On Mon, Jan 21, 2013 at 2:45 PM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:
>
>> RECOVERED_EDITS is not a column family.  It should be ignored by hbck.
>>
>> Filed a jira:
>>
>> https://issues.apache.org/jira/browse/HBASE-764<https://issues.apache.org/jira/browse/HBASE-7640>
>
>
> Thanks Jimmy.  That makes sense now you mention it (smile).
> St.Ack
>

Thats right.  Its a bug in hbck that it thinks recovered.edits a cf.
St.Ack
On Mon, Jan 21, 2013 at 4:03 PM, Jean-Marc Spaggiari <
[EMAIL PROTECTED]> wrote:

> Ok, so basically, there was no issues with my tables? I did not used
> any specific keywors for my CF... They are all called "@" or "A" ;)
>
> 2013/1/21, Stack <[EMAIL PROTECTED]>:
> > On Mon, Jan 21, 2013 at 2:45 PM, Jimmy Xiang <[EMAIL PROTECTED]>
> wrote:
> >
> >> RECOVERED_EDITS is not a column family.  It should be ignored by hbck.
> >>
> >> Filed a jira:
> >>
> >> https://issues.apache.org/jira/browse/HBASE-764<
> https://issues.apache.org/jira/browse/HBASE-7640>
> >
> >
> > Thanks Jimmy.  That makes sense now you mention it (smile).
> > St.Ack
> >
>