You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/09/13 09:18:20 UTC
[jira] [Created] (HADOOP-13599) s3a close() to be non-synchronized,
so avoid risk of deadlock on shutdown
Steve Loughran created HADOOP-13599:
---------------------------------------
Summary: 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
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: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org