[
https://issues.apache.org/jira/browse/HADOOP-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607130#comment-17607130
]
Daniel Carl Jones edited comment on HADOOP-18448 at 9/20/22 11:37 AM:
----------------------------------------------------------------------
As Steve linked, the region configuration was only added in HADOOP-17705 and
released in Apache Hadoop 3.3.2. [Reviewing the EMR
versions|https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-release-app-versions-6.x.html],
emr-6.5.0 is based on Hadoop 3.2.1 (as is all versions up to emr-6.8.0, the
version available today). So there's no way for you today to configure the
signing region with the version of S3A in emr-6.5.0.
[~einavhol], to continue using S3A you would need Amazon EMR to publish a new
release with changes from a newer version of Apache Hadoop - at least those
changes released in Hadoop 3.3.2. Alternatively, use the EmrFS connector
(s3://) if they have solved this issue already.
was (Author: JIRAUSER284792):
As Steve linked, the region configuration was only added in HADOOP-17705 and
released in Apache Hadoop 3.3.2. [Reviewing the EMR
versions|https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-release-app-versions-6.x.html],
emr-6.5.0 is based on Hadoop 3.2.1 (as is all versions up to emr-6.8.0, the
version available today). So there's no way for you today to configure the
signing region with the version of S3A in emr-6.5.0.
[~einavhol], to continue using S3A you would need Amazon EMR to publish a new
release with a newer version of Apache Hadoop - at least Hadoop 3.3.2.
Alternatively, use the EmrFS connector (s3://) if they have solved this issue
already.
> s3a endpoint per bucket configuration in pyspark is ignored
> -----------------------------------------------------------
>
> Key: HADOOP-18448
> URL: https://issues.apache.org/jira/browse/HADOOP-18448
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Environment: Amazon EMR emr-6.5.0 cluster
> Reporter: Einav Hollander
> Priority: Major
>
> I'm using EMR emr-6.5.0 cluster in us-east-1 with ec2 instances. cluster is
> running spark application using pyspark 3.2.1
> EMR is using Hadoop distribution:Amazon 3.2.1
> my spark application is reading from one bucket in us-west-2 and writing to a
> bucket in us-east-1.
> since I'm processing a large amount of data I'm paying a lot of money for the
> network transport . in order to reduce the cost I have create a vpc interface
> to s3 endpoint in us-west-2. inside the spark application I'm using aws cli
> for reading the file names from us-west-2 bucket and it is working through
> the s3 interface endpoint but when I use pyspark to read the data it is using
> the us-east-1 s3 endpoint instead of the us-west-2 endpoint.
> I tried to use per bucket configuration but it is being ignored although I
> added it to the defualt configuration and to spark submit call.
> I tried to set the following configuration but they are ignored:
> '--conf',
> "spark.hadoop.fs.s3a.aws.credentials.provider=com.amazonaws.auth.DefaultAWSCredentialsProviderChain",
> '--conf', "spark.hadoop.fs.s3a.impl=org.apache.hadoop.fs.s3a.S3AFileSystem",
> '--conf', "spark.hadoop.fs.s3a.bucket.<us-west-2-bucket -name>.endpoint=<my
> vpc endpoint>",
> '--conf', "spark.hadoop.fs.s3a.bucket.<us-west-2-bucket
> -name>.endpoint.region=us-west-2",
> '--conf', "spark.hadoop.fs.s3a.bucket.<us-east-1-bucket -name>.endpoint=<vpc
> gateway endpoint>",
> '--conf', "spark.hadoop.fs.s3a.bucket.<us-east-1-bucket
> -name>.endpoint.region=us-east-1",
> '--conf', "spark.hadoop.fs.s3a.path.style.access=false"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
