[
https://issues.apache.org/jira/browse/IMPALA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956153#comment-16956153
]
Steve Loughran commented on IMPALA-9058:
----------------------------------------
Happens if the DDB table is present but that doesn't contain a s3guard Version
marker. HADOOP-16520 has just done a lot of work handling race conditions in
cluster setup, and the ability to recover from unintentional deletion of these
markers.
If you saw the stack trace on a build of Hadoop without this patch, I'd say
retry patch version to see if that fixes it.
If you saw it in a patch which does (and it was only committed anywhere in the
last week), then you may have found a regression.
> S3 tests failing with FileNotFoundException getVersionMarkerItem on ../VERSION
> ------------------------------------------------------------------------------
>
> Key: IMPALA-9058
> URL: https://issues.apache.org/jira/browse/IMPALA-9058
> Project: IMPALA
> Issue Type: Test
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Critical
>
> I've seen this happen several times now, S3 tests intermittently fail with an
> error such as:
> {code:java}
> Query aborted:InternalException: Error adding partitions E CAUSED BY:
> MetaException: java.io.IOException: Got exception:
> java.io.FileNotFoundException getVersionMarkerItem on ../VERSION:
> com.amazonaws.services.dynamodbv2.model.ResourceNotFoundException: Requested
> resource not found (Service: AmazonDynamoDBv2; Status Code: 400; Error Code:
> ResourceNotFoundException; Request ID:
> 8T9IS939MDI7ASOB0IJCC34J3NVV4KQNSO5AEMVJF66Q9ASUAAJG) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
