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

Wenzhe Zhou commented on IMPALA-8754:
-------------------------------------

Saw the same error on a recent run for following test - 
TestScannersFuzzing.test_fuzz_alltypes

with error message:
*07:25:41* E   ImpalaBeeswaxException: ImpalaBeeswaxException:*07:25:41* E    
Query aborted:Disk I/O error on 
impala-ec2-centos74-m5-4xlarge-ondemand-1edc.vpc.cloudera.com:22001: Failed to 
open HDFS file 
s3a://impala-test-uswest2-1/test-warehouse/test_fuzz_alltypes_35f4e1d.db/alltypes/year=2010/month=10/101001.txt*07:25:41*
 E   Error(2): No such file or directory*07:25:41* E   Root cause: 
ResourceNotFoundException: Requested resource not found (Service: 
AmazonDynamoDBv2; Status Code: 400; Error Code: ResourceNotFoundException; 
Request ID: BQBKHGMTM98GCBISATM7UG15MNVV4KQNSO5AEMVJF66Q9ASUAAJG)

> 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
>            Assignee: Joe McDonnell
>            Priority: Critical
>              Labels: broken-build, flaky
>
> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to