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 2020/01/14 14:39:00 UTC

[jira] [Commented] (HADOOP-16800) ITestDynamoDBMetadataStore.testTableVersioning failure -DDB deleteItem consistency?

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

Steve Loughran commented on HADOOP-16800:
-----------------------------------------

{code}
[ERROR] testTableVersioning(org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStore)  Time elapsed: 11.559 s  <<< FAILURE! java.lang.AssertionError: Version marker should be null after deleting it from the table. expected null, but was:<{ Item: {parent=../VERSION, table_created=1579008995010, table_version=100, child=../VERSION} }>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotNull(Assert.java:755)
	at org.junit.Assert.assertNull(Assert.java:737)
	at org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStore.deleteVersionMarkerItem(ITestDynamoDBMetadataStore.java:763)
	at org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStore.checkVerifyVersionMarkerCompatibility(ITestDynamoDBMetadataStore.java:679)
	at org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStore.testTableVersioning(ITestDynamoDBMetadataStore.java:662)
	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.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}


> ITestDynamoDBMetadataStore.testTableVersioning failure -DDB deleteItem consistency?
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-16800
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16800
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> transient failure of ITestDynamoDBMetadataStore.testTableVersioning; the deleted table version record was still there.
> Looks like the delete is EC; finally I hit a consistency event
> Proposed: the test iterates a bit awaiting the exception



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org