hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aggarwal, Vaibhav" <>
Subject RE: org.apache.hadoop.fs.ChecksumException: Checksum error:
Date Sat, 20 Aug 2011 00:57:52 GMT
This is a really curious case.

How many replicas of each block do you have?

Are you able to copy the data directly using HDFS client?
You could try the hadoop fs -copyToLocal command and see if it can copy the data from hdfs

That would help you verify that the issue really is at HDFS layer (though it does look like
that from the stack trace).

Which file format are you using?


-----Original Message-----
From: W S Chung [] 
Sent: Friday, August 19, 2011 3:26 PM
Subject: org.apache.hadoop.fs.ChecksumException: Checksum error:

For some reason, my questions sent two days ago again never shows up, even though I can google
the question. I apologize if you have seen this question before.

After loading around 2G or so data in a few files into hive, the "select count(*) from table"
query keep failing. The JobTracker UI gives the following error:

     org.apache.hadoop.fs.ChecksumException: Checksum error:
at 51794944
       at org.apache.hadoop.fs.FSInputChecker.verifySum(
       at org.apache.hadoop.fs.FSInputChecker.readChecksumChunk(
       at org.apache.hadoop.fs.FSInputChecker.read1(
       at org.apache.hadoop.hdfs.DFSClient$
       at org.apache.hadoop.hdfs.DFSClient$DFSInputStream.readBuffer(
       at org.apache.hadoop.hdfs.DFSClient$
       at org.apache.hadoop.util.LineReader.readLine(
       at org.apache.hadoop.mapred.MapTask$TrackedRecordReader.moveToNext(
       at org.apache.hadoop.mapred.MapTask$
       at org.apache.hadoop.mapred.MapTask.runOldMapper(
       at org.apache.hadoop.mapred.Child.main(

fsck reports there are courrpted blocks. I have tried dropping the table and reload a few
time. As far as I can see, the behavior is somewhat different every time, in the sense of
how many corrupted blocks and how many files I loaded before the corrupted blocks appear.
Sometimes the corrupted blocks show up after the data is loaded and sometimes only after the
"select count(*)" query is made. I have tried setting "io.skip.checksum.errors" to true, but
has no effect at all.

I know that checksum error is usually an indication of hardware problem. But we are running
hive on NFS cluster and has ECC memory.
Our system admin here is not willing to believe that our high quality hardware has so many
issues. I did try installing a simpler single node hive on another machine and the problem
does not appear in this install after the data is loaded. Can someone give me some pointers
in what else to try? Thanks.

View raw message