d, Is there anyway to get the corrupted file name?
>>
>> Block encoding is "NONE", table schema has bloom filter as "ROW",
>> compression type is "Snappy" and durability is SKIP_WAL.
>>
>>
>> Regards,
>> Pankaj
>>
>>
&g
om: Ted Yu [mailto:yuzhih...@gmail.com]
Sent: Saturday, January 14, 2017 9:41 AM
To: d...@hbase.apache.org
Cc: user@hbase.apache.org
Subject: Re: Region comapction failed
w.r.t. #2, I did a quick search for bloom related fixes.
I found HBASE-13123 but it was in 1.0.2
Planning to spend more time in the nex
is "Snappy" and durability is SKIP_WAL.
>
>
> Regards,
> Pankaj
>
>
> -Original Message-
> From: Ted Yu [mailto:yuzhih...@gmail.com]
> Sent: Friday, January 13, 2017 10:30 PM
> To: d...@hbase.apache.org
> Cc: user@hbase.apache.org
> Subject: Re: R
ema has bloom filter as "ROW", compression
type is "Snappy" and durability is SKIP_WAL.
Regards,
Pankaj
-Original Message-
From: Ted Yu [mailto:yuzhih...@gmail.com]
Sent: Friday, January 13, 2017 10:30 PM
To: d...@hbase.apache.org
Cc: user@hbase.apache.org
S
In the second case, the error happened when writing hfile. Can you track down
the path of the new file so that further investigation can be done ?
Does the table use any encoding ?
Thanks
> On Jan 13, 2017, at 2:47 AM, Pankaj kr wrote:
>
> Hi,
>
> We met a weird issue in our production envir
Hi,
We met a weird issue in our production environment.
Region compaction is always failing with following errors,
1.
2017-01-10 02:19:10,427 | ERROR |
regionserver/RS-HOST/RS-IP:PORT-longCompactions-1483858654825 | Compaction
failed Request = regionName=., storeName=XYZ, fileCount=6, fil
