[
https://issues.apache.org/jira/browse/HADOOP-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029823#comment-18029823
]
ASF GitHub Bot commented on HADOOP-18944:
-----------------------------------------
hadoop-yetus commented on PR #6203:
URL: https://github.com/apache/hadoop/pull/6203#issuecomment-3402709946
:broken_heart: **-1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|:----:|----------:|--------:|:--------:|:-------:|
| +0 :ok: | reexec | 0m 0s | | Docker mode activated. |
| -1 :x: | patch | 0m 17s | |
https://github.com/apache/hadoop/pull/6203 does not apply to trunk. Rebase
required? Wrong Branch? See
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help.
|
| Subsystem | Report/Notes |
|----------:|:-------------|
| GITHUB PR | https://github.com/apache/hadoop/pull/6203 |
| Console output |
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6203/1/console |
| versions | git=2.34.1 |
| Powered by | Apache Yetus 0.14.0 https://yetus.apache.org |
This message was automatically generated.
> 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]
