[
https://issues.apache.org/jira/browse/HADOOP-19512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938274#comment-17938274
]
Steve Loughran commented on HADOOP-19512:
-----------------------------------------
write to S3 express buckets always create an UploadContentProviders recreation
message.
{code}
bin/hadoop fs -touchz s3a://stevel--euw1-az3--x-s3/file
2025-03-25 16:16:13,590 [main] INFO impl.UploadContentProviders
(UploadContentProviders.java:newStream(289)) - Stream recreated:
FileWithOffsetContentProvider{file=/tmp/hadoop-stevel/s3a/s3ablock-0001-8452225509461160677.tmp,
offset=0} BaseContentProvider{size=0, initiated at 2025-03-25T16:16:13.567,
streamCreationCount=2, currentStream=null}
{code}
This is something to investigate in future. This message should only be printed
if there's a second attempt to upload any data. Is this happening? and if not,
what is unusual about writing here?
> S3A: Test failures testing with unusual bucket configurations
> -------------------------------------------------------------
>
> Key: HADOOP-19512
> URL: https://issues.apache.org/jira/browse/HADOOP-19512
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.5.0, 3.4.2
> Reporter: Steve Loughran
> Assignee: Ahmar Suhail
> Priority: Minor
> Attachments: test-failures.txt
>
>
> 1. The logic to skip vector IO contract tests doesn't work if the analytics
> stream is set on a per-bucket basis for the test bucket
> 2. tests with SSE-C are failing. Test bucket is normally set up to use
> SSE-KMS, FWIW
> {code}
> <property>
> <name>fs.s3a.bucket.stevel-london.encryption.algorithm</name>
> <value>SSE-KMS</value>
> </property>
> {code}
> this only happens when the analytics stream is set for the test bucket
> fs.s3a.bucket.stevel-london.input.stream.type=analytics; set it globally all
> is good
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
