[ 
https://issues.apache.org/jira/browse/HADOOP-18889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766859#comment-17766859
 ] 

Steve Loughran commented on HADOOP-18889:
-----------------------------------------

and a few more to skip. one finding is that those exploring options 
(encryption, storage class) only fail after the fs is created. Move the checks 
into createConfiguration() and all will be good. or maybe we add an override 
point in S3ABaseT

h2. TestS3ACannedACLs



{code}
[ERROR] testCreatedObjectsHaveACLs(org.apache.hadoop.fs.s3a.ITestS3ACannedACLs) 
 Time elapsed: 2.574 s  <<< ERROR!
org.apache.hadoop.fs.s3a.AWSBadRequestException: PUT 0-byte object  on test:  
The XML you provided was not well-formed or did not validate against our 
published schema. (Service: Amazon S3; Status Code: 400; Error Code: 
MalformedACLError; Request ID: 0c07c874:18a4af9cc87:2069a:2d; S3 Extended 
Request ID: null; Proxy: null), S3 Extended Request ID: null:MalformedACLError: 
The XML you provided was not well-formed or did not validate against our 
published schema. (Service: Amazon S3; Status Code: 400; Error Code: 
MalformedACLError; Request ID: 0c07c874:18a4af9cc87:2069a:2d; S3 Extended 
Request ID: null; Proxy: null)

{code}

h2. ITestXAttrCost


{code}
[ERROR] testXAttrRoot(org.apache.hadoop.fs.s3a.impl.ITestXAttrCost)  Time 
elapsed: 1.959 s  <<< FAILURE!
java.lang.AssertionError: 
[Headers on root object] 
Expecting:
  <["header.Content-Length", "header.x-amz-storage-class"]>
to contain only:
  <["header.Content-Length", "header.Content-Type"]>
elements not found:
  <["header.Content-Type"]>
and elements not expected:
  <["header.x-amz-storage-class"]>



{code}
think we should just make that test not worry about it.


h2. ITestS3AEncryptionSSEKMSDefaultKey
{code}
[ERROR] 
testEncryptionSettingPropagation(org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSDefaultKey)
  Time elapsed: 2.122 s  <<< ERROR!
org.apache.hadoop.fs.s3a.AWSBadRequestException: PUT 0-byte object  on 
fork-0001/test: Invalid Request (Service: Amazon S3; Status Code: 400; Error 
Code: InvalidRequest; Request ID: 0c07c870:18a4aea24fc:1ffdb:323; S3 Extended 
Request ID: null; Proxy: null), S3 Extended Request ID: null:InvalidRequest: 
Invalid Request (Service: Amazon S3; Status Code: 400; Error Code: 
InvalidRequest; Request ID: 

{code}

h2. ITestS3AConcurrentOps timeouts

just a slow long haul test run against a store not being that responsive. just 
need to mark as scale/increase timeouts.
{code}
[ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
1,733.925 s <<< FAILURE! - in 
org.apache.hadoop.fs.s3a.scale.ITestS3AConcurrentOps
[ERROR] 
testThreadPoolCoolDown(org.apache.hadoop.fs.s3a.scale.ITestS3AConcurrentOps)  
Time elapsed: 960.026 s  <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 960000 
milliseconds
        at java.lang.Thread.sleep(Native Method)
        at 
org.apache.hadoop.fs.s3a.scale.ITestS3AConcurrentOps.testThreadPoolCoolDown(ITestS3AConcurrentOps.java:199)
        at java.lang.Thread.run(Thread.java:750)

{code}



> 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: Ahmar Suhail
>            Priority: Critical
>
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to