[
https://issues.apache.org/jira/browse/HADOOP-18889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776488#comment-17776488
]
ASF GitHub Bot commented on HADOOP-18889:
-----------------------------------------
virajjasani commented on code in PR #6180:
URL: https://github.com/apache/hadoop/pull/6180#discussion_r1363203939
##########
hadoop-common-project/hadoop-common/src/main/resources/core-default.xml:
##########
@@ -1596,14 +1596,15 @@
<property>
<name>fs.s3a.connection.establish.timeout</name>
- <value>5000</value>
- <description>Socket connection setup timeout in milliseconds.</description>
+ <value>5s</value>
+ <description>Socket connection setup timeout in milliseconds; this will be
retried
+ more than once.</description>
</property>
<property>
<name>fs.s3a.connection.timeout</name>
- <value>200000</value>
- <description>Socket connection timeout in milliseconds.</description>
+ <value>200s</value>
+ <description>Socket connection timeout.</description>
Review Comment:
For both of them, is it valuable to mention in the description that
milliseconds is the default unit unless user specifies any other unit
explicitly?
> S3A: V2 SDK client does not work with third-party store
> -------------------------------------------------------
>
> Key: HADOOP-18889
> URL: https://issues.apache.org/jira/browse/HADOOP-18889
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> testing against an external store without specifying region now blows up
> because the region is queried off eu-west-1.
> What are we do to here? require the region setting *which wasn't needed
> before? what even region do we provide for third party stores?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]