HADOOP-17705. S3A to add Config to set AWS region #3020
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mukund-thakur
approved these changes
May 18, 2021
|
LGTM, will wait for yetus to become green. |
added 2 commits
May 18, 2021 12:54
|
+1 pending docs. |
|
in docs, if we have a stack trace of the error message you get before this patch is in, add it to the troubleshooting doc with a reference to the option as well |
|
LGTM; just need to strip out the EOLs for a merge from the web UI. |
|
🎊 +1 overall
This message was automatically generated. |
|
merged to trunk, backporting if the new test runs OK there |
asfgit
pushed a commit
that referenced
this pull request
May 24, 2021
The option `fs.s3a.endpoint.region` can be used to explicitly set the AWS region of a bucket. This is needed when using AWS Private Link, as the region cannot be automatically determined. Contributed by Mehakmeet Singh Change-Id: I4b52f85d7af0ddd56b2b0505ac0124d4fcc67ca0
kiran-maturi
pushed a commit
to kiran-maturi/hadoop
that referenced
this pull request
Nov 24, 2021
The option `fs.s3a.endpoint.region` can be used to explicitly set the AWS region of a bucket. This is needed when using AWS Private Link, as the region cannot be automatically determined. Contributed by Mehakmeet Singh
SimonYang-CS
pushed a commit
to SimonYang-CS/hadoop
that referenced
this pull request
Dec 16, 2021
The option `fs.s3a.endpoint.region` can be used to explicitly set the AWS region of a bucket. This is needed when using AWS Private Link, as the region cannot be automatically determined. Contributed by Mehakmeet Singh
SimonYang-CS
pushed a commit
to SimonYang-CS/hadoop
that referenced
this pull request
Dec 24, 2021
The option `fs.s3a.endpoint.region` can be used to explicitly set the AWS region of a bucket. This is needed when using AWS Private Link, as the region cannot be automatically determined. Contributed by Mehakmeet Singh
jojochuang
pushed a commit
to jojochuang/hadoop
that referenced
this pull request
May 23, 2023
…#3020) The option `fs.s3a.endpoint.region` can be used to explicitly set the AWS region of a bucket. This is needed when using AWS Private Link, as the region cannot be automatically determined. Contributed by Mehakmeet Singh Change-Id: If9b1b1d8ea3556ed4dfb2d164a8a6fa477dfc36d (cherry picked from commit 27d27beb319bcbee7d89514b6cd7ba88e325019b)
jojochuang
pushed a commit
to jojochuang/hadoop
that referenced
this pull request
May 23, 2023
…apache#3020)" This reverts commit 203b7c2.
jojochuang
pushed a commit
to jojochuang/hadoop
that referenced
this pull request
May 23, 2023
…#3020) The option `fs.s3a.endpoint.region` can be used to explicitly set the AWS region of a bucket. This is needed when using AWS Private Link, as the region cannot be automatically determined. Contributed by Mehakmeet Singh *Important* This has proven to be a fairly brittle change. Consult the CDPD-26441 JIRA for details. Test environments with the AWS CLI or run in EC2 do not pick up regressions, so it is unlikely that test runs will identify major issues which surfaced in production. When backported it MUST be accompanied by: CDPD-27264. HADOOP-17771. S3AFS creation fails "Unable to find a region via the region provider chain." This patch depends on CDPD-21205, which breaks the HBoss build/test. Read the instructions there when cherrypicking. Change-Id: If9b1b1d8ea3556ed4dfb2d164a8a6fa477dfc36d
jojochuang
pushed a commit
to jojochuang/hadoop
that referenced
this pull request
May 23, 2023
…on via the region provider chain." (apache#3133) This addresses the regression in Hadoop 3.3.1 where if no S3 endpoint is set in fs.s3a.endpoint, S3A filesystem creation may fail on non-EC2 deployments, depending on the local host environment setup. * If fs.s3a.endpoint is empty/null, and fs.s3a.endpoint.region is null, the region is set to "us-east-1". * If fs.s3a.endpoint.region is explicitly set to "" then the client falls back to the SDK region resolution chain; this works on EC2 * Details in troubleshooting.md, including a workaround for Hadoop-3.3.1+ * Also contains some minor restructuring of troubleshooting.md * uses pre-Auditing LogExactlyOnce import, so doesn't depend on that patch. Contributed by Steve Loughran. This is a critical follow on patch to CDPD-26441. HADOOP-17705. S3A to add Config to set AWS region (apache#3020) Both patches must be included Change-Id: Icca928e1752423d68591508c360ff6434997fb64
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tested by: mvn clean verify -Dparallel-tests -Dscale
Region: ap-south-1
Test:
Timeout and intermittent failures.
CC: @steveloughran @mukund-thakur