[ 
https://issues.apache.org/jira/browse/IMPALA-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Takiar resolved IMPALA-9996.
----------------------------------
    Resolution: Duplicate

Looks like a duplicate of IMPALA-8754 and IMPALA-9058

> An S3 test failing with ResourceNotFoundException
> -------------------------------------------------
>
>                 Key: IMPALA-9996
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9996
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Fang-Yu Rao
>            Assignee: Sahil Takiar
>            Priority: Critical
>              Labels: broken-build, flaky
>
> In a recent S3 build, we have seen that 
> [test_tpcds_count|https://github.com/apache/impala/blob/master/tests/query_test/test_tpcds_queries.py#L52-L53]
>  
> ([https://github.com/apache/impala/blob/master/testdata/workloads/tpcds/queries/count.test#L114-L119])
>  failed with {{ResourceNotFoundException}}.
> The issue may be related to IMPALA-9058.
> The error message in {{impalad.INFO}} (under the directory of {{ee_tests}}) 
> is as follows.
> {code:java}
> I0722 10:31:44.524209 13047 coordinator.cc:684] ExecState: query 
> id=7d4f684028848784:ad2f6f0e00000000 
> finstance=7d4f684028848784:ad2f6f0e00000001 on 
> host=impala-ec2-centos74-m5-4xlarge-ondemand-1230.vpc.cloudera.com:22002 
> (EXECUTING -> ERROR) status=Disk I/O error on 
> impala-ec2-centos74-m5-4xlarge-ondemand-1230.vpc.cloudera.com:22002: Failed 
> to open HDFS file 
> s3a://impala-test-uswest2-1/test-warehouse/tpcds.store_sales_parquet/ss_sold_date_sk=2451752/d245f3a054fd2c66-f7f7052200000004_1984874558_data.0.parq
> Error(2): No such file or directory
> Root cause: ResourceNotFoundException: Requested resource not found (Service: 
> AmazonDynamoDBv2; Status Code: 400; Error Code: ResourceNotFoundException; 
> Request ID: G9QMA17VTSIKOQK33V9TDGMF13VV4KQNSO5AEMVJF66Q9ASUAAJG)
> {code}
> Maybe [~stakiar] and [~joemcdonnell] could offer some insight into it. Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to