hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabor Bota (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15888) ITestDynamoDBMetadataStore can leak (large) DDB tables in test failures/timeout
Date Fri, 14 Dec 2018 16:08:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721563#comment-16721563
] 

Gabor Bota commented on HADOOP-15888:
-------------------------------------

Would that be a good solution to move ITestDynamoDBMetadataStore in the scale test category?
In HADOOP-15426 [~stevel@apache.org] you already moved ITestDynamoDBMetadataStore to the sequential
tests. Should I move it to the scale tests?

> ITestDynamoDBMetadataStore can leak (large) DDB tables in test failures/timeout
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-15888
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15888
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.1.2
>            Reporter: Steve Loughran
>            Priority: Major
>         Attachments: Screen Shot 2018-10-30 at 17.32.43.png
>
>
> This is me doing some backporting of patches from branch-3.2, so it may be an intermediate
condition but
> # I'd noticed I wasn't actually running ITestDynamoDBMetadataStore
> # so I set it up to work with teh right config opts (table and region)
> # but the tests were timing out
> # looking at DDB tables in the AWS console showed a number of DDB tables "testProvisionTable",
"testProvisionTable", created, each with "500 read, 100 write capacity (i.e. ~$50/month)
> I haven't replicated this in trunk/branch-3.2 itself, but its clearly dangerous. At the
very least, we should have a size of 1 R/W in all creations, so the cost of a test failure
is neglible, and then we should document the risk and best practise.
> Also: use "s3guard" as the table prefix to make clear its origin



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

---------------------------------------------------------------------
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