You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/05/07 17:10:55 UTC

[GitHub] [incubator-druid] gianm commented on issue #6905: Druid 0.13.0 - Warning on Historicals "Not all bytes were read from the S3ObjectInputStream"

gianm commented on issue #6905: Druid 0.13.0 - Warning on Historicals "Not all bytes were read from the S3ObjectInputStream"
URL: https://github.com/apache/incubator-druid/issues/6905#issuecomment-490168049
 
 
   I've seen it too. Looking at the source of S3AbortableInputStream, this happens when a stream is closed without all bytes being read. I'm not sure what the cause might be. Maybe something in S3DataSegmentPuller that isn't fully reading the stream?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org