[ https://issues.apache.org/jira/browse/HADOOP-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043570#comment-16043570 ]
Aaron Fabbri commented on HADOOP-14283: --------------------------------------- Thanks [~liuml07]. I ran into the same problem when testing with S3Guard. I ended up using a ranged version for it, as I found it hard to find the list of dynamodblocal releases: {code} <dependency> <groupId>com.amazonaws</groupId> <artifactId>DynamoDBLocal</artifactId> <version>[1.11.86,2.0)</version> </dependency> {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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org