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

Steve Loughran commented on HADOOP-14283:
-----------------------------------------

OK, +1 for the patch without the scale test;

rename the JIRA to something about "upgrade to AWS SDK ..." once in, make a 
dependency of HADOOP-9991, & the S3A phase III so we can keep an eye on where 
it surfaces. 

FWIW, Rajesh has [an ongoing AWS 
patch|https://github.com/aws/aws-sdk-java/pull/1105#issuecomment-306279002] 
which I think would be good to pick up in some future AWS release. But as they 
come out so often, we can wait

> S3A may hang due to bug in AWS SDK 1.11.86
> ------------------------------------------
>
>                 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
>         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]

Reply via email to