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 2019/06/11 14:33:00 UTC
[jira] [Commented] (HADOOP-16362)
ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle fails if test bucket
isn't on demand
[ https://issues.apache.org/jira/browse/HADOOP-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861104#comment-16861104 ]
Steve Loughran commented on HADOOP-16362:
-----------------------------------------
reported by [~gabor.bota]
{code}
[ERROR] Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 182.223 s <<< FAILURE! - in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB
[ERROR] testDynamoDBInitDestroyCycle(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB) Time elapsed: 20.077 s <<< FAILURE!
java.lang.AssertionError:
Expected a java.io.IOException to be thrown, but got the result: : Metadata Store Diagnostics:
ARN=arn:aws:dynamodb:eu-west-1:360379543683:table/gabota-versioned-bucket-ireland
billing-mode=provisioned
description=S3Guard metadata store in DynamoDB
name=gabota-versioned-bucket-ireland
persist.authoritative.bit=true
read-capacity=100
region=eu-west-1
retryPolicy=ExponentialBackoffRetry(maxRetries=9, sleepTime=100 MILLISECONDS)
size=44232
status=ACTIVE
table={AttributeDefinitions: [{AttributeName: child,AttributeType: S}, {AttributeName: parent,AttributeType: S}],TableName: gabota-versioned-bucket-ireland,KeySchema: [{AttributeName: parent,KeyType: HASH}, {AttributeName: child,KeyType: RANGE}],TableStatus: ACTIVE,CreationDateTime: Tue Jun 11 10:27:01 CEST 2019,ProvisionedThroughput: {NumberOfDecreasesToday: 0,ReadCapacityUnits: 100,WriteCapacityUnits: 100},TableSizeBytes: 44232,ItemCount: 260,TableArn: arn:aws:dynamodb:eu-west-1:360379543683:table/gabota-versioned-bucket-ireland,TableId: dc15974b-0686-4173-96b1-05412d549047,}
write-capacity=100
at org.apache.hadoop.test.LambdaTestUtils.intercept(LambdaTestUtils.java:499)
at org.apache.hadoop.test.LambdaTestUtils.intercept(LambdaTestUtils.java:384)
at org.apache.hadoop.test.LambdaTestUtils.intercept(LambdaTestUtils.java:453)
at org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle(ITestS3GuardToolDynamoDB.java:223)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)
{code}
> ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle fails if test bucket isn't on demand
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-16362
> URL: https://issues.apache.org/jira/browse/HADOOP-16362
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> After HADOOP-15563, if the default s3guard bucket for an FS isn't on-demand, then {{ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle}} fails.
> This is because it creates an on-demand DDB table using a dynamodb// ref, but then calls set-capacity on the original FS URL -which then uses any existing table if it is present. And if that table is provisioned, the set capacity call succeeds.
> Fix: the set-capacity call to take the dynamodb:// URL too
--
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