You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2023/03/02 17:24:00 UTC

[jira] [Comment Edited] (IMPALA-11816) Flaky TestEventProcessing tests

    [ https://issues.apache.org/jira/browse/IMPALA-11816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695835#comment-17695835 ] 

Michael Smith edited comment on IMPALA-11816 at 3/2/23 5:23 PM:
----------------------------------------------------------------

Hit an instance of this in https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/18818/testReport/junit/metadata.test_event_processing/TestEventProcessing/test_event_based_replication/.


was (Author: JIRAUSER288956):
Hit an incident of this in https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/18818/testReport/junit/metadata.test_event_processing/TestEventProcessing/test_event_based_replication/.

> Flaky TestEventProcessing tests
> -------------------------------
>
>                 Key: IMPALA-11816
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11816
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>    Affects Versions: Impala 4.3.0
>            Reporter: Tamas Mate
>            Priority: Major
>
> h3. Failing tests are:
> metadata.test_event_processing.TestEventProcessing.test_transactional_insert_events
> metadata.test_event_processing.TestEventProcessing.test_event_based_replication
> h3. Error Message
> {code:none}
> metadata/test_event_processing.py:176:
>    in test_event_based_replication self.__run_event_based_replication_tests()
> metadata/test_event_processing.py:223:
>    in __run_event_based_replication_tests
> 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 38523 within 10 seconds
> {code}
> h3. Stacktrace
> {code:none}
> metadata/test_event_processing.py:176:
>    in test_event_based_replication self.__run_event_based_replication_tests()
> metadata/test_event_processing.py:223:
>    in __run_event_based_replication_tests
> 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 38523 within 10 seconds
> {code}
> h3. Standard Error
> {code:none}
> SET client_identifier=metadata/test_event_processing.py::TestEventProcessing::()::test_event_based_replication;
> -- connecting to: localhost:21000 --
> 2022-12-27 13:08:41,389 INFO MainThread: Could not connect to ('::1', 21000, 0, 0)
> Traceback (most recent call last):
>    File "/data/jenkins/workspace/impala-cdwh-2022.0.11.1-core-asan/Impala-Toolchain/toolchain-packages-gcc7.5.0/thrift-0.11.0-p5/python/lib/python2.7/site-packages/thrift/transport/TSocket.py", line 104, in open handle.connect(sockaddr)
>    File "/data/jenkins/workspace/impala-cdwh-2022.0.11.1-core-asan/Impala-Toolchain/toolchain-packages-gcc7.5.0/python-2.7.16/lib/python2.7/socket.py", line 228, in meth 
>       return getattr(self._sock,name)(*args) error:
> [Errno 111] Connection refused
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org