[
https://issues.apache.org/jira/browse/HADOOP-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531260#comment-15531260
]
Hudson commented on HADOOP-13599:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10510 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10510/])
HADOOP-13599. s3a close() to be non-synchronized, so avoid risk of (cnauroth:
rev 47f80922dc7cb2fa6d084e6fb1f354c4ec1d4c69)
* (edit)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3AConfiguration.java
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java
> s3a close() to be non-synchronized, so avoid risk of deadlock on shutdown
> -------------------------------------------------------------------------
>
> Key: HADOOP-13599
> URL: https://issues.apache.org/jira/browse/HADOOP-13599
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.7.3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 2.8.0
>
> Attachments: HADOOP-13599-branch-2-001.patch,
> HADOOP-13599-branch-2-002.patch, HADOOP-13599-branch-2-003.patch
>
>
> We've had a report of hive deadlocking on teardown, as a synchronous FS close
> was blocking shutdown threads, similar to HADOOP-3139
> S3a close needs to be made non-synchronized. All we need is some code to
> prevent re-entrancy at the start; easily done
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
