[IMPALA-5387] Excessive logging to INFO and ERROR files when reading S3 data

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Impala 2.9.0
• Component/s: Backend
• Epic Color: ghx-label-1
• Assignee: Pranay Singh
• Reporter: Mostafa Mokhtar
• Created: 30/May/17 18:56
• Updated: 07/Nov/17 11:27
• Resolved: 06/Nov/17 22:10

Description

While querying data in S3 the impalad.ERROR file is flooded with the messages like the one below, are those expected?

UnsupportedOperationException: Byte-buffer read unsupported by input streamjava.lang.UnsupportedOperationException: Byte-buffer read unsupported by input stream
	at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:150)
readDirect: FSDataInputStream#read error:
UnsupportedOperationException: Byte-buffer read unsupported by input streamjava.lang.UnsupportedOperationException: Byte-buffer read unsupported by input stream
	at org.apache.hadoop.fs.FSDataInputStream.read(FSDataInputStream.java:150)

Same thing for impalad.INFO

W0529 13:48:46.398718  9771 S3AbortableInputStream.java:163] Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use.
W0529 13:48:46.420027  9767 S3AbortableInputStream.java:163] Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use.
W0529 13:48:46.429368  9758 S3AbortableInputStream.java:163] Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use.