Hi,
There are no inconsistencies in hbck output and no corrupt blocks in fsck
output.
But getting the same exception (after getting some results) during scanning for
rows in the particular regions.
Thanks.
Meeran
On Fri, 10 Jul 2020 17:45:13 +0530 Viraj Jasani wrote
Hi Meeran,
BlockHeaders output has NegativeArraySizeException while reading a block.
Did you try scanning the table or specific rowkey range from the region? Is
it all good?
Also, since you were able to upgrade the cluster to 2.2.4, I am assuming
all services are good, but can you once confirm
Hi Sean,
We upgraded the cluster to latest stable version HBase-2.2.4. We are still
facing the issue. Any help on this please?
Thanks,
Meeran
On Mon, 06 Jul 2020 14:24:16 +0530 test gmail test
wrote
Hi Sean,
printblocks output - https://pastebin.com/EYUpi6LL
Integer.MAX_VALUE, andlead to overflowerror.
--原始邮件--
发件人:"Mohamed Meeran"<mailto:meeran.gladiat...@gmail.com;;
发送时间:2020年7月3日(星期五) 晚上10:26
收件人:"user"<mailto:user@hbase.apache.org;;
主题:Could not iterate StoreFileScanner - during compa
Hi Sean,
printblocks output - https://pastebin.com/EYUpi6LL
blockheaders output - https://pastebin.com/TJBqgwsp
We are yet to test it on HBase-2.2. Will upgrade the cluster and let you know.
Thanks for the help.
Regards,
Meeran
On Sat, 04 Jul 2020 05:26:46 +0530 Sean Busbey
Hi,
"cur=10259783_10101578851/hb:B/1490097148981/Put/vlen=16591695"
"Invalid onDisksize=-969694035: expected to be at least 33 and at most
2147483647, or -1"
I guess there is a very big cell causethe block size exceed
theInteger.MAX_VALUE, andlead to overflowerror.
File attachments won't work on the mailing list. Can you put the files on
some hosting service?
Can you reproduce the problem on hbase 2.2? HBase 2.1 has been EOM since
May.
On Fri, Jul 3, 2020, 18:20 Mohamed Meeran
wrote:
> Hi,
>
> We are using HBase-2.1.9 (Hadoop-3.1.3) in our setup. In the
Hi,
We are using HBase-2.1.9 (Hadoop-3.1.3) in our setup. In the logs, we see
major compaction failed for some of the regions with the following error
logs.
Caused by: java.io.IOException: Could not iterate
StoreFileScanner[HFileScanner for reader