Hi all

While digging through /hbase folder in HDFS, I found WAL folder that is
splitting and last modified time is 2 weeks ago (I changed the node name in
this example)
*drwxr-xr-x   - hbase hbase          0 2015-02-11 18:16
/hbase/.logs/<node2>,60020,1417575124373-splitting*

Is this case common? After reading about log splitting, my understanding is
this folder should disappear after successful recovery. CMIIW.

Best regards,

Arinto


Arinto
www.otnira.com

On Tue, Feb 24, 2015 at 11:45 AM, Arinto Murdopo <ari...@gmail.com> wrote:

>
> On Tue, Feb 24, 2015 at 9:46 AM, Jean-Marc Spaggiari <
> jean-m...@spaggiari.org> wrote:
>
> > I don't have the list of the corrupted files yet. I notice that when I
>> try
>> > to Get some of the files, my HBase client code throws these exceptions:
>> > org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after
>> > attempts=2, exceptions:
>> > Mon Feb 23 17:49:32 SGT 2015,
>> > org.apache.hadoop.hbase.client.HTable$3@11ff4a1c,
>> > org.apache.hadoop.hbase.NotServingRegionException:
>> > org.apache.hadoop.hbase.NotServingRegionException: Region is not online:
>> >
>> >
>> plr_sg_insta_media_live,\x0177998597896:953:5:a5:58786,1410771627251.6c323832d2dc77c586f1cf6441c7ef6e.
>> >
>>
>> FSCK should give ou the list of corrupt files. Can you extract it from
>> there?
>>
>
> Yup, I managed to extract them. We have corrupt files as well as missing
> files. Luckily there's no .regionfile corrupted or missing. I'll read more
> about HFile before updating this thread more. :)
>
>
>> >
>> > Can I use these exceptions to determine the corrupted files?
>> > The files are media data (images or videos) obtained from the internet.
>> >
>>
>> This exception gives you all the hints for a directory most probably under
>> /hbase/plr_sg_insta_media_live/6c323832d2dc77c586f1cf6441c7ef6e
>>
>> Files under this directory might be corrupted but you need to find which
>> files. If it's a HFiles it's easy. If it's the .regioninfo it's a bit more
>> tricky.
>
>
>
>
> Arinto
> www.otnira.com
>

Reply via email to