[
https://issues.apache.org/jira/browse/HADOOP-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17822675#comment-17822675
]
ASF GitHub Bot commented on HADOOP-19097:
-----------------------------------------
virajjasani commented on PR #6601:
URL: https://github.com/apache/hadoop/pull/6601#issuecomment-1973645133
Change looks good, until we remove fs.s3a settings from core-default, i
wonder if we should do one round of comparison b/ s3a/Contants and core-default
(as a followup jira)?
> core-default fs.s3a.connection.establish.timeout value too low -warning
> always printed
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-19097
> URL: https://issues.apache.org/jira/browse/HADOOP-19097
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Labels: pull-request-available
>
> caused by HADOOP-18915.
> in core-default we set the value of fs.s3a.connection.establish.timeout to 5s
> {code}
> <property>
> <name>fs.s3a.connection.establish.timeout</name>
> <value>5s</value>
> </property>
> {code}
> but there is a minimum of 15s, so this prints a warning
> {code}
> 2024-02-29 10:39:27,369 WARN impl.ConfigurationHelper: Option
> fs.s3a.connection.establish.timeout is too low (5,000 ms). Setting to 15,000
> ms instead
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
