Hi,
I'm getting this error when trying to read from HFiles:
http://pastebin.com/SJci7uQM
Any idea what's going on here?
Thanks!
Hi Donmai,
Seems to be something wrong with this file. Can you try to reach the
HFile ? Try to check cluster with hbck tool
(http://hbase.apache.org/book.html#hbck), use -details flag to see the
errors.
2015-05-12 16:02 GMT+03:00 donmai :
> Hi,
>
> I'm getting this error when trying to read from
What release of hbase are you using ?
Please read http://hbase.apache.org/book.html#hfile where you can find
description about HFile tool. This tool would allow you to investigate
given HFile.
Cheers
On Tue, May 12, 2015 at 6:02 AM, donmai wrote:
> Hi,
>
> I'm getting this error when trying to
Thanks for the help! I am getting 'okay' for everything. I am using S3 for
the store, do you think it could be an issue with how S3 is reading the
files?
On Tue, May 12, 2015 at 9:45 AM, Talat Uyarer wrote:
> Hi Donmai,
>
> Seems to be something wrong with this file. Can you try to reach the
> H
Thanks Ted, this actually helped me out alot! I'm running 0.98.6 and was
able to determine that the HFiles are perfectly okay and can be scanned
through without issue - it looks like there's something else going on,
since after a compaction everything works...
On Tue, May 12, 2015 at 9:55 AM, Ted
Actually, looking deeper into it, things don't seem to be making sense.
The error message is this: Caused by: java.io.IOException: Positional read
of 65723 bytes failed at offset 394218 (returned 16384)
As such, I try to do a read for 65723 bytes using the tool to see if it
fails at that offset:
-w is shorthand for --seekToRow (so it is not offset):
-w,--seekToRow Seek to this row and print all the kvs for this
row only
Do you store all your data on s3 ?
Cheers
On Tue, May 12, 2015 at 8:50 AM, donmai wrote:
> Actually, looking deeper into it, things do
Ahhh, thanks for that. Yep, all flushes will (or should be) going to S3.
I'm working through it and it seems that it's defaulting to the positional
read instead of seek+read - is this accurate?
On Tue, May 12, 2015 at 12:00 PM, Ted Yu wrote:
> -w is shorthand for --seekToRow (so it is not offset
Hi Ted - would you happen to have any insight as to what issues might cause
a positional read failure for an HFile? Running the HFile tool seems to
have normal output.
On Wed, May 13, 2015 at 12:40 PM, donmai wrote:
> Ahhh, thanks for that. Yep, all flushes will (or should be) going to S3.
> I'm
I tried to access http://pastebin.com/SJci7uQM (from your first email) but
looks like the file has been removed.
Can you post the error on pastebin again ?
Cheers
On Wed, May 20, 2015 at 9:38 PM, donmai wrote:
> Hi Ted - would you happen to have any insight as to what issues might cause
> a po
s3:// and s3n:// are different things. Given the structure of your S3 key,
I think you should be using s3n.
For reference, http://wiki.apache.org/hadoop/AmazonS3
11 matches
Mail list logo