[
https://issues.apache.org/jira/browse/HADOOP-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036361#comment-18036361
]
ASF GitHub Bot commented on HADOOP-19654:
-----------------------------------------
mukund-thakur commented on PR #7882:
URL: https://github.com/apache/hadoop/pull/7882#issuecomment-3504444626
reading about the stack trace, the reason for failure is both s3client and
the create bucket request should have the same configured region.
Debugging more I found we should be setting the region here as well
https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/tools/ITestBucketTool.java#L115
once set it will get propagated as location constraint in the create bucket
request.
but even if setting and verifying that propagation is happening correctly,
it fails with the same reason.
Yes just accepting both error, the test will be fine and I am wondering what
is going on.
> Upgrade AWS SDK to 2.35.4
> -------------------------
>
> Key: HADOOP-19654
> URL: https://issues.apache.org/jira/browse/HADOOP-19654
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, fs/s3
> Affects Versions: 3.5.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
>
> Upgrade to a recent version of 2.33.x or later while off the critical path of
> things.
> HADOOP-19485 froze the sdk at a version which worked with third party stores.
> Apparently the new version works; early tests show that Bulk Delete calls
> with third party stores complain about lack of md5 headers, so some tuning is
> clearly going to be needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
