You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (JIRA)" <ji...@apache.org> on 2019/07/12 00:15:00 UTC
[jira] [Created] (IMPALA-8754) S3 with S3Guard tests encounter
"ResourceNotFoundException" from DynamoDB
Joe McDonnell created IMPALA-8754:
-------------------------------------
Summary: S3 with S3Guard tests encounter "ResourceNotFoundException" from DynamoDB
Key: IMPALA-8754
URL: https://issues.apache.org/jira/browse/IMPALA-8754
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 3.3.0
Reporter: Joe McDonnell
When running tests on s3 with s3guard, various tests can encounter the following error coming from the DynamoDB:
{noformat}
E Query aborted:Disk I/O error on impala-ec2-centos74-m5-4xlarge-ondemand-02c8.vpc.cloudera.com:22002: Failed to open HDFS file s3a://impala-test-uswest2-1/test-warehouse/tpcds.store_sales_parquet/ss_sold_date_sk=2451718/6843d8a91fc5ae1d-88b2af4b00000004_156969840_data.0.parq
E Error(2): No such file or directory
E Root cause: ResourceNotFoundException: Requested resource not found (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX){noformat}
Tests that have seen this (this is flaky):
* TestTpcdsQuery.test_tpcds_count
* TestHdfsFdCaching.test_caching_disabled_by_param
* TestMtDop.test_compute_stats
* TestScanRangeLengths.test_scan_ranges
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)