You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/09/20 19:36:20 UTC
[jira] [Updated] (HADOOP-13262) set multipart delete timeout to 5 *
60s in S3ATestUtils.createTestFileSystem
[ https://issues.apache.org/jira/browse/HADOOP-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-13262:
------------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
> set multipart delete timeout to 5 * 60s in S3ATestUtils.createTestFileSystem
> ----------------------------------------------------------------------------
>
> Key: HADOOP-13262
> URL: https://issues.apache.org/jira/browse/HADOOP-13262
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 2.8.0
> Environment: parallel test runs
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-13262-001.patch
>
>
> HADOOP-13139 patch 003 test runs show that the multipart tests are failing on parallel runs. The cause of this is that the FS init logic in {{S3ATestUtils.createTestFileSystem}} sets the expiry to 0: any in-progress multipart uploads will fail.
> setting a 5 minute expiry will clean up from old runs, but not break anything in progress.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org