You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/12/04 18:31:00 UTC
[jira] [Resolved] (IMPALA-9058) S3 tests failing with
FileNotFoundException getVersionMarkerItem on ../VERSION
[ https://issues.apache.org/jira/browse/IMPALA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-9058.
-----------------------------------
Resolution: Won't Fix
We will be disabling S3guard for tests since S3 now has strong consistency - https://aws.amazon.com/s3/consistency/
> S3 tests failing with FileNotFoundException getVersionMarkerItem on ../VERSION
> ------------------------------------------------------------------------------
>
> Key: IMPALA-9058
> URL: https://issues.apache.org/jira/browse/IMPALA-9058
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Sahil Takiar
> Assignee: Tim Armstrong
> Priority: Critical
> Labels: broken-build, flaky
>
> 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)