[
https://issues.apache.org/jira/browse/IMPALA-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153806#comment-17153806
]
Wenzhe Zhou commented on IMPALA-8754:
-------------------------------------
Saw the similar error in data loading tpch for Kudu.
The console output show the data loading failure when loading tpch for Kudu
Loading workload 'tpch' using exploration strategy 'core' in table formats
'kudu/none/none'. Logging to
/data/jenkins/workspace/impala-asf-master-core-s3/repos/Impala/logs/data_loading/data-load-tpch-core-kudu_none_none.log*04:14:39*
Error loading data.
Log file
logs/data_loading/sql/tpch/load-tpch-core-impala-generated-kudu-none-node.sql.log
show the root cause was requested resource not found. See log file below:
ERROR: INSERT INTO TABLE tpch_kudu.lineitem SELECT * FROM tpch.lineitem
Traceback (most recent call last):
File
"/data/jenkins/workspace/impala-asf-master-core-s3/repos/Impala/bin/load-data.py",
line 208, in exec_impala_query_from_file
result = impala_client.execute(query)
File
"/data/jenkins/workspace/impala-asf-master-core-s3/repos/Impala/tests/beeswax/impala_beeswax.py",
line 187, in execute
handle = self.__execute_query(query_string.strip(), user=user)
File
"/data/jenkins/workspace/impala-asf-master-core-s3/repos/Impala/tests/beeswax/impala_beeswax.py",
line 365, in __execute_query
self.wait_for_finished(handle)
File
"/data/jenkins/workspace/impala-asf-master-core-s3/repos/Impala/tests/beeswax/impala_beeswax.py",
line 386, in wait_for_finished
raise ImpalaBeeswaxException("Query aborted:" + error_log, None)
ImpalaBeeswaxException: ImpalaBeeswaxException:
Query aborted:Disk I/O error on
impala-ec2-centos74-m5-4xlarge-ondemand-1b61.vpc.cloudera.com:22000: Failed to
open HDFS file
s3a://impala-test-uswest2-1/test-warehouse/tpch.lineitem/lineitem.tbl
Error(2): No such file or directory
Root cause: ResourceNotFoundException: Requested resource not found (Service:
AmazonDynamoDBv2; Status Code: 400; Error Code: ResourceNotFoundException;
Request ID: JNG4VO47DND18BRTPCROK2H38FVV4KQNSO5AEMVJF66Q9ASUAAJG)
> 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]
