[
https://issues.apache.org/jira/browse/IMPALA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176302#comment-17176302
]
Zoltán Borók-Nagy commented on IMPALA-9058:
-------------------------------------------
Also saw a disk I/O error for TestCoordinators.test_multiple_coordinators in an
S3 core build. Following Aman I'm reporting it here since IMPALA-8754 is closed
as a duplicate of this.
{noformat}
custom_cluster/test_coordinators.py:72: in test_multiple_coordinators
self.execute_query_expect_success(client2, "select * from
functional.alltypes");
common/impala_test_suite.py:811: in wrapper
return function(*args, **kwargs)
common/impala_test_suite.py:819: in execute_query_expect_success
result = cls.__execute_query(impalad_client, query, query_options, user)
common/impala_test_suite.py:909: in __execute_query
return impalad_client.execute(query, user=user)
common/impala_connection.py:205: in execute
return self.__beeswax_client.execute(sql_stmt, user=user)
beeswax/impala_beeswax.py:205: in execute
result = self.fetch_results(query_string, handle)
beeswax/impala_beeswax.py:452: in fetch_results
exec_result = self.__fetch_results(query_handle, max_rows)
beeswax/impala_beeswax.py:463: in __fetch_results
results = self.__do_rpc(lambda: self.imp_service.fetch(handle, False,
fetch_rows))
beeswax/impala_beeswax.py:520: in __do_rpc
raise ImpalaBeeswaxException(self.__build_error_message(b), b)
E ImpalaBeeswaxException: ImpalaBeeswaxException:
E INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
E MESSAGE: Disk I/O error on
impala-ec2-centos74-m5-4xlarge-ondemand-1f97.vpc.cloudera.com:22002: Failed to
open HDFS file
s3a://impala-test-uswest2-1/test-warehouse/alltypes/year=2009/month=4/090401.txt
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:
U2NQE3ATV7RAE7J4FITSIP5I7JVV4KQNSO5AEMVJF66Q9ASUAAJG){noformat}
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
