[
https://issues.apache.org/jira/browse/HADOOP-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043740#comment-16043740
]
Mingliang Liu commented on HADOOP-14283:
----------------------------------------
yeah we may need this in next merge from trunk to s3guard; or perhaps we can
get this change in HADOOP-13345 branch now?
After applying the change, I merged from trunk locally and run the integration
tests against both -Ddynamo (us-west-1 region) and -Ddynamodblocal, all tests
pass.
{code}
$ mvn -Dit.test='ITestS3A*,ITestS3Guard*,ITestDynamo*' -Dtest=none -Ds3guard
-Ddynamodblocal -q verify
Results :
Tests run: 391, Failures: 0, Errors: 0, Skipped: 59
$ mvn -Dit.test='ITestS3A*,ITestS3Guard*,ITestDynamo*' -Dtest=none -Ds3guard
-Ddynamo -q verify
Results :
Tests run: 391, Failures: 0, Errors: 0, Skipped: 59
{code}
> Upgrade AWS SDK to 1.11.134
> ---------------------------
>
> Key: HADOOP-14283
> URL: https://issues.apache.org/jira/browse/HADOOP-14283
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 3.0.0-alpha2
> Reporter: Aaron Fabbri
> Assignee: Aaron Fabbri
> Priority: Critical
> Fix For: 2.9.0, 3.0.0-alpha4
>
> Attachments: HADOOP-14283.001.patch, ITestS3AConcurrentRename.java
>
>
> We hit a hang bug when testing S3A with parallel renames.
> I narrowed this down to the newer AWS Java SDK. It only happens under load,
> and appears to be a failure to wake up a waiting thread on timeout/error.
> I've created a github issue here:
> https://github.com/aws/aws-sdk-java/issues/1102
> I can post a Hadoop scale test which reliably reproduces this after some
> cleanup. I have posted an SDK-only test here which reproduces the issue
> without Hadoop:
> https://github.com/ajfabbri/awstest
> I have a support ticket open and am working with Amazon on this bug so I'll
> take this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
