[
https://issues.apache.org/jira/browse/IMPALA-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702525#comment-17702525
]
Daniel Becker commented on IMPALA-10983:
----------------------------------------
[~csringhofer] unfortunately it seems the problem is not solved, the same
builds now fail with
{code:java}
metadata/test_event_processing.py:43: in test_insert_events
self.run_test_insert_events(unique_database)
metadata/test_event_processing.py:115: in run_test_insert_events
EventProcessorUtils.wait_for_event_processing(self)
util/event_processor_utils.py:91: in wait_for_event_processing
EventProcessorUtils.wait_for_synced_event_id(timeout, current_event_id)
util/event_processor_utils.py:63: in wait_for_synced_event_id
raise Exception("Event processor is not working. Status:
{0}".format(status))
E Exception: Event processor is not working. Status: ERROR{code}
The same error also occurs in
{*}metadata.test_event_processing.TestEventProcessing.test_event_based_replication{*}.
This error message was introduced in the commit for this issue.
> 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]
