[
https://issues.apache.org/jira/browse/HADOOP-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029822#comment-18029822
]
ASF GitHub Bot commented on HADOOP-18944:
-----------------------------------------
mehakmeet opened a new pull request, #6203:
URL: https://github.com/apache/hadoop/pull/6203
### Description of PR
Changing the default value of async drain threshold from read-ahead's
default value to actual async drain threshold default value.
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> 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]
