[
https://issues.apache.org/jira/browse/HADOOP-18221?focusedWorklogId=767938&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767938
]
ASF GitHub Bot logged work on HADOOP-18221:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/May/22 15:07
Start Date: 09/May/22 15:07
Worklog Time Spent: 10m
Work Description: dannycjones commented on PR #4294:
URL: https://github.com/apache/hadoop/pull/4294#issuecomment-1121225748
@ahmarsuhail In `trunk`, Steve recently introduced a threshold for moving
the drain to a synchronous operation.
https://github.com/apache/hadoop/blob/e0cd0a82e032b926774dcea69edd4fa20aae2603/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java#L612-L623
Can we create a JIRA to add it after rebase?
Issue Time Tracking
-------------------
Worklog Id: (was: 767938)
Time Spent: 0.5h (was: 20m)
> stream warns Not all bytes were read from the S3ObjectInputStream when closed
> -----------------------------------------------------------------------------
>
> Key: HADOOP-18221
> URL: https://issues.apache.org/jira/browse/HADOOP-18221
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Ahmar Suhail
> Assignee: Ahmar Suhail
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Issue: [https://github.com/aws/aws-sdk-java/issues/1211] has resurfaced in
> the prefetching stream when it is closed before reading for blocks is
> complete. This can be fixed by draining the stream before closingÂ
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
