[
https://issues.apache.org/jira/browse/HADOOP-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028494#comment-18028494
]
ASF GitHub Bot commented on HADOOP-18944:
-----------------------------------------
github-actions[bot] commented on PR #6203:
URL: https://github.com/apache/hadoop/pull/6203#issuecomment-3383635750
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> s3a openfile is using readahead rather than async drain threshold to
> calculate drain threshold
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-18944
> URL: https://issues.apache.org/jira/browse/HADOOP-18944
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 3.3.6
> Reporter: Steve Loughran
> Priority: Minor
> Labels: pull-request-available
>
> we are using the wrong default value for the async drain threshold in
> {{org.apache.hadoop.fs.s3a.impl.OpenFileSupport}}
> {code}
> builderSupport.getPositiveLong(ASYNC_DRAIN_THRESHOLD,
> defaultReadAhead))
> {code}
> this means the drain threshold isn't being taken up in random io unless you
> have a very small readahead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
