hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13262) set multipart delete timeout to 5 * 60s in S3ATestUtils.createTestFileSystem
Date Mon, 13 Jun 2016 15:17:21 GMT

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

Steve Loughran updated HADOOP-13262:
------------------------------------
    Attachment: HADOOP-13262-001.patch

5 minute delay. That number is completely spurious; just bigger than 0 and long enough not
to be likely to cause problems. We could extend it

> 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


Mime
View raw message