impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mostafa Mokhtar (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IMPALA-5387) Excessive logging to INFO and ERROR files when reading S3 data
Date Tue, 30 May 2017 18:57:04 GMT
Mostafa Mokhtar created IMPALA-5387:
---------------------------------------

             Summary: Excessive logging to INFO and ERROR files when reading S3 data
                 Key: IMPALA-5387
                 URL: https://issues.apache.org/jira/browse/IMPALA-5387
             Project: IMPALA
          Issue Type: Bug
          Components: Backend
    Affects Versions: Impala 2.9.0
            Reporter: Mostafa Mokhtar
            Assignee: Sailesh Mukil
            Priority: Critical
             Fix For: Impala 2.9.0


While querying data in S3 the impalad.ERROR file is flooded with the messages like the one
below, are those expected?
{code}
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)
{code}

Same thing for impalad.INFO
{code}
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.
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message