hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-13826) [s3a] Deadlock possible using Amazon S3 SDK
Date Mon, 21 Nov 2016 20:16:00 GMT
Sean Mackrory created HADOOP-13826:

             Summary: [s3a] Deadlock possible using Amazon S3 SDK
                 Key: HADOOP-13826
                 URL: https://issues.apache.org/jira/browse/HADOOP-13826
             Project: Hadoop Common
          Issue Type: Bug
            Reporter: Sean Mackrory

In testing HIVE-15093 we have encountered deadlocks in the s3a connector. The TransferManager
javadocs (http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/transfer/TransferManager.html)
explain how this is possible:

{quote}It is not recommended to use a single threaded executor or a thread pool with a bounded
work queue as control tasks may submit subtasks that can't complete until all sub tasks complete.
Using an incorrectly configured thread pool may cause a deadlock (I.E. the work queue is filled
with control tasks that can't finish until subtasks complete but subtasks can't execute because
the queue is filled).{quote}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

View raw message