[
https://issues.apache.org/jira/browse/HADOOP-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057704#comment-16057704
]
Steve Loughran commented on HADOOP-14564:
-----------------------------------------
Main issue is that the socket timeout, 200s, is > than the test timeout of
180s; any hang will fail the test at the JUnit level, rather than have the
failures raise in the test run & have it handle it.
Short-term workaround: set the values to be shorter.
{code}
<property>
<name>fs.s3a.connection.establish.timeout</name>
<value>15000</value>
</property>
<property>
<name>fs.s3a.connection.socket.timeout</name>
<value>${fs.s3a.connection.establish.timeout}</value>
</property>
{code}
> s3a test can hang in teardown with network problems
> ---------------------------------------------------
>
> Key: HADOOP-14564
> URL: https://issues.apache.org/jira/browse/HADOOP-14564
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 2.8.1
> Reporter: Steve Loughran
> Priority: Minor
>
> If you've a transient network test and things fail, then the directory
> cleanup in teardown can block a test so that it times out entirely.
> Proposed: shorten socket timeouts for s3 connections, assuming this is
> possible (stack trace implies it was in a read(), not a connect()).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
