[
https://issues.apache.org/jira/browse/IMPALA-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701520#comment-17701520
]
ASF subversion and git services commented on IMPALA-10983:
----------------------------------------------------------
Commit a6333aed6b0fe2cf355aeaa1952735b9208b2f43 in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=a6333aed6 ]
IMPALA-10983: Wait more in wait_for_event_processing if there is progress
There are some flaky tests where wait_for_event_processing timeouts,
e.g. TestEventProcessing.test_insert_events. My theory is that this
is caused by parallel tests with DDL/DML statements that can also
fire HMS events that have to be processed by catalogd.
The change bumps (default: 10 sec->100 sec) the timeout in case
there is some progress in event processing. If still the same
event is processed then the old timeout is used.
An alternative approach would be to mark the related test as serial,
but I would prefer to avoid this as it would make test jobs slower.
The event processor status is also checked to timeout earlier if
the event processor is without hope of recovery.
Change-Id: I676854f7df9aea5fa10fb6ecf6381195bc8fa4b8
Reviewed-on: http://gerrit.cloudera.org:8080/19614
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Test metadata.test_event_processing.TestEventProcessing.test_insert_events
> fails
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-10983
> URL: https://issues.apache.org/jira/browse/IMPALA-10983
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Daniel Becker
> Assignee: Csaba Ringhofer
> Priority: Blocker
> Labels: build-failure
>
> Test
> {code:java}
> metadata.test_event_processing.TestEventProcessing.test_insert_events {code}
> fails:
> h3. Error Message
> {code:java}
> metadata/test_event_processing.py:48: in test_insert_events
> self.run_test_insert_events(unique_database)
> metadata/test_event_processing.py:128: in run_test_insert_events
> EventProcessorUtils.wait_for_event_processing(self)
> util/event_processor_utils.py:61: in wait_for_event_processing within {1}
> seconds".format(current_event_id, timeout)) E Exception: Event processor did
> not sync till last known event id 31772 within 10 seconds{code}
> h3. Stacktrace
> {code:java}
> metadata/test_event_processing.py:48: in test_insert_events
> self.run_test_insert_events(unique_database)
> metadata/test_event_processing.py:128: in run_test_insert_events
> EventProcessorUtils.wait_for_event_processing(self)
> util/event_processor_utils.py:61: in wait_for_event_processing within {1}
> seconds".format(current_event_id, timeout)) E Exception: Event processor did
> not sync till last known event id 31772 within 10 seconds{code}
> h3. Standard Error
> {code:java}
> SET
> client_identifier=metadata/test_event_processing.py::TestEventProcessing::()::test_insert_events;
> -- connecting to: localhost:21000 -- connecting to localhost:21050 with
> impyla -- 2021-10-22 15:28:00,639 INFO MainThread: Closing active operation
> -- connecting to localhost:28000 with impyla -- 2021-10-22 15:28:00,665 INFO
> MainThread: Closing active operation -- connecting to localhost:11050 with
> impyla SET
> client_identifier=metadata/test_event_processing.py::TestEventProcessing::()::test_insert_events;
> SET sync_ddl=False; -- executing against localhost:21000 DROP DATABASE IF
> EXISTS `test_insert_events_4293827b` CASCADE; -- 2021-10-22 15:28:03,902 INFO
> MainThread: Started query e74933cd62ece6eb:63eb608100000000 SET
> client_identifier=metadata/test_event_processing.py::TestEventProcessing::()::test_insert_events;
> SET sync_ddl=False; -- executing against localhost:21000{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
