[jira] [Updated] (HADOOP-14621) S3A client raising ConnectionPoolTimeoutException in test

2018-07-26 Thread Steve Loughran (JIRA)


 [ 
https://issues.apache.org/jira/browse/HADOOP-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-14621:

Parent Issue: HADOOP-15620  (was: HADOOP-15220)

> S3A client raising ConnectionPoolTimeoutException in test
> -
>
> Key: HADOOP-14621
> URL: https://issues.apache.org/jira/browse/HADOOP-14621
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3, test
>Affects Versions: 3.0.0-beta1
> Environment: Home network with 2+ other users on high bandwidth 
> activities
>Reporter: Steve Loughran
>Priority: Minor
>
> Parallel test with threads = 12 triggering connection pool timeout. 
> Hypothesis? Congested network triggering pool timeout.
> Fix? For tests, could increase pool size
> For retry logic, this should be considered retriable, even on idempotent 
> calls (as its a failure to acquire a connection



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14621) S3A client raising ConnectionPoolTimeoutException in test

2018-02-15 Thread Steve Loughran (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-14621:

Parent Issue: HADOOP-15220  (was: HADOOP-14831)

> S3A client raising ConnectionPoolTimeoutException in test
> -
>
> Key: HADOOP-14621
> URL: https://issues.apache.org/jira/browse/HADOOP-14621
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3, test
>Affects Versions: 3.0.0-beta1
> Environment: Home network with 2+ other users on high bandwidth 
> activities
>Reporter: Steve Loughran
>Priority: Major
>
> Parallel test with threads = 12 triggering connection pool timeout. 
> Hypothesis? Congested network triggering pool timeout.
> Fix? For tests, could increase pool size
> For retry logic, this should be considered retriable, even on idempotent 
> calls (as its a failure to acquire a connection



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14621) S3A client raising ConnectionPoolTimeoutException in test

2018-02-15 Thread Steve Loughran (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-14621:

Summary: S3A client raising ConnectionPoolTimeoutException in test  (was: 
S3A client raising ConnectionPoolTimeoutException)

> S3A client raising ConnectionPoolTimeoutException in test
> -
>
> Key: HADOOP-14621
> URL: https://issues.apache.org/jira/browse/HADOOP-14621
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3, test
>Affects Versions: 3.0.0-beta1
> Environment: Home network with 2+ other users on high bandwidth 
> activities
>Reporter: Steve Loughran
>Priority: Major
>
> Parallel test with threads = 12 triggering connection pool timeout. 
> Hypothesis? Congested network triggering pool timeout.
> Fix? For tests, could increase pool size
> For retry logic, this should be considered retriable, even on idempotent 
> calls (as its a failure to acquire a connection



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14621) S3A client raising ConnectionPoolTimeoutException in test

2018-02-15 Thread Steve Loughran (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-14621:

Priority: Minor  (was: Major)

> S3A client raising ConnectionPoolTimeoutException in test
> -
>
> Key: HADOOP-14621
> URL: https://issues.apache.org/jira/browse/HADOOP-14621
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3, test
>Affects Versions: 3.0.0-beta1
> Environment: Home network with 2+ other users on high bandwidth 
> activities
>Reporter: Steve Loughran
>Priority: Minor
>
> Parallel test with threads = 12 triggering connection pool timeout. 
> Hypothesis? Congested network triggering pool timeout.
> Fix? For tests, could increase pool size
> For retry logic, this should be considered retriable, even on idempotent 
> calls (as its a failure to acquire a connection



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14621) S3A client raising ConnectionPoolTimeoutException

2018-02-13 Thread Steve Loughran (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-14621:

Parent Issue: HADOOP-14831  (was: HADOOP-14531)

> S3A client raising ConnectionPoolTimeoutException
> -
>
> Key: HADOOP-14621
> URL: https://issues.apache.org/jira/browse/HADOOP-14621
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3, test
>Affects Versions: 3.0.0-beta1
> Environment: Home network with 2+ other users on high bandwidth 
> activities
>Reporter: Steve Loughran
>Priority: Major
>
> Parallel test with threads = 12 triggering connection pool timeout. 
> Hypothesis? Congested network triggering pool timeout.
> Fix? For tests, could increase pool size
> For retry logic, this should be considered retriable, even on idempotent 
> calls (as its a failure to acquire a connection



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-14621) S3A client raising ConnectionPoolTimeoutException

2018-02-13 Thread Steve Loughran (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-14621:

Priority: Major  (was: Minor)

> S3A client raising ConnectionPoolTimeoutException
> -
>
> Key: HADOOP-14621
> URL: https://issues.apache.org/jira/browse/HADOOP-14621
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3, test
>Affects Versions: 3.0.0-beta1
> Environment: Home network with 2+ other users on high bandwidth 
> activities
>Reporter: Steve Loughran
>Priority: Major
>
> Parallel test with threads = 12 triggering connection pool timeout. 
> Hypothesis? Congested network triggering pool timeout.
> Fix? For tests, could increase pool size
> For retry logic, this should be considered retriable, even on idempotent 
> calls (as its a failure to acquire a connection



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org