[IMPALA-8500] test_timestamp_out_of_range fails with NoSuchObjectException: test_timestamp_out_of_range_dc37915d on S3

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: Impala 3.3.0
• Component/s: Infrastructure
• Labels: broken-build
• Target Version: Impala 3.4.0
• Epic Color: ghx-label-4
• Assignee: Joe McDonnell
• Reporter: Tim Armstrong
• Created: 06/May/19 16:19
• Updated: 19/Feb/20 20:21
• Resolved: 19/Feb/20 20:21

Description

I'm not sure what to make of this. Maybe you have an idea:

Error Message
test setup failure
Stacktrace
conftest.py:319: in cleanup
    {'sync_ddl': sync_ddl})
common/impala_test_suite.py:620: in wrapper
    return function(*args, **kwargs)
common/impala_test_suite.py:628: in execute_query_expect_success
    result = cls.__execute_query(impalad_client, query, query_options, user)
common/impala_test_suite.py:722: in __execute_query
    return impalad_client.execute(query, user=user)
common/impala_connection.py:180: in execute
    return self.__beeswax_client.execute(sql_stmt, user=user)
beeswax/impala_beeswax.py:187: in execute
    handle = self.__execute_query(query_string.strip(), user=user)
beeswax/impala_beeswax.py:362: in __execute_query
    handle = self.execute_query_async(query_string, user=user)
beeswax/impala_beeswax.py:356: in execute_query_async
    handle = self.__do_rpc(lambda: self.imp_service.query(query,))
beeswax/impala_beeswax.py:516: in __do_rpc
    raise ImpalaBeeswaxException(self.__build_error_message(b), b)
E   ImpalaBeeswaxException: ImpalaBeeswaxException:
E    INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
E    MESSAGE: ImpalaRuntimeException: Error making 'dropDatabase' RPC to Hive Metastore: 
E   CAUSED BY: NoSuchObjectException: test_timestamp_out_of_range_dc37915d

It does look like it created the database and used it fine:

-- 2019-05-02 11:09:21,883 INFO     MainThread: Started query e847e67be097c2a0:6c29d4f400000000
SET client_identifier=query_test/test_scanners.py::TestParquet::()::test_timestamp_out_of_range[protocol:beeswax|exec_option:{'batch_size':0;'num_nodes':0;'disable_codegen_rows_threshold':0;'disable_codegen':False;'abort_on_error':1;'debug_action':None;'exec_single_node_rows_t;
-- executing against localhost:21000
use test_timestamp_out_of_range_dc37915d;

-- 2019-05-02 11:09:22,266 INFO     MainThread: Started query ab498d07351289b2:03f6198300000000
SET client_identifier=query_test/test_scanners.py::TestParquet::()::test_timestamp_out_of_range[protocol:beeswax|exec_option:{'batch_size':0;'num_nodes':0;'disable_codegen_rows_threshold':0;'disable_codegen':False;'abort_on_error':1;'debug_action':None;'exec_single_node_rows_t;
SET batch_size=0;
SET num_nodes=0;
SET disable_codegen_rows_threshold=0;
SET disable_codegen=False;
SET abort_on_error=1;
SET exec_single_node_rows_threshold=0;
-- executing against localhost:21000
SELECT * FROM out_of_range_timestamp;

-- 2019-05-02 11:09:22,273 INFO     MainThread: Started query be4886563821196f:871eb37f00000000
-- executing against localhost:21000
SELECT * FROM out_of_range_time_of_day;

Maybe some S3 consistency issue?

Issue Links

• relates to: IMPALA-8344 Add support for running S3 tests with S3Guard