liubingxing opened a new pull request, #4179:
URL: https://github.com/apache/hadoop/pull/4179

   In [HDFS-16538](http://https//issues.apache.org/jira/browse/HDFS-16538) , we 
found an EC file decoding bug if more than one data block read failed. 
   
   Currently, we found another bug trigger by #StatefulStripeReader.decode.
   
   If we read an EC file which **length more than one stripe**, and this file 
have **one data block** and **the first parity block** corrupted, this error 
will happen.
   
   ```java
   org.apache.hadoop.HadoopIllegalArgumentException: Invalid buffer found, not 
allowing null    at 
org.apache.hadoop.io.erasurecode.rawcoder.ByteBufferDecodingState.checkOutputBuffers(ByteBufferDecodingState.java:132)
       at 
org.apache.hadoop.io.erasurecode.rawcoder.ByteBufferDecodingState.<init>(ByteBufferDecodingState.java:48)
       at 
org.apache.hadoop.io.erasurecode.rawcoder.RawErasureDecoder.decode(RawErasureDecoder.java:86)
       at 
org.apache.hadoop.io.erasurecode.rawcoder.RawErasureDecoder.decode(RawErasureDecoder.java:170)
       at 
org.apache.hadoop.hdfs.StripeReader.decodeAndFillBuffer(StripeReader.java:435)
       at 
org.apache.hadoop.hdfs.StatefulStripeReader.decode(StatefulStripeReader.java:94)
       at org.apache.hadoop.hdfs.StripeReader.readStripe(StripeReader.java:392)
       at 
org.apache.hadoop.hdfs.DFSStripedInputStream.readOneStripe(DFSStripedInputStream.java:315)
       at 
org.apache.hadoop.hdfs.DFSStripedInputStream.readWithStrategy(DFSStripedInputStream.java:408)
       at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:918) 
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to