[
https://issues.apache.org/jira/browse/HADOOP-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889148#comment-16889148
]
Hudson commented on HADOOP-15847:
---------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16957 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16957/])
HADOOP-15847. S3Guard testConcurrentTableCreations to set R/W capacity (stevel:
rev cd967c75a76bea81304e4e6a2bf9c75145230e81)
* (edit) hadoop-tools/hadoop-aws/src/test/resources/core-site.xml
* (edit) hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
* (edit)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/ITestS3GuardConcurrentOps.java
> S3Guard testConcurrentTableCreations to set r & w capacity == 0
> ---------------------------------------------------------------
>
> Key: HADOOP-15847
> URL: https://issues.apache.org/jira/browse/HADOOP-15847
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: lqjacklee
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HADOOP-15847-001.patch, HADOOP-15847-002.patch
>
>
> I just found a {{testConcurrentTableCreations}} DDB table lurking in a
> region, presumably from an interrupted test. Luckily
> test/resources/core-site.xml forces the r/w capacity to be 10, but it could
> still run up bills.
> Recommend
> * explicitly set capacity = 1 for the test
> * and add comments in the testing docs about keeping cost down.
> I think we may also want to make this a scale-only test, so it's run less
> often
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
