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 "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2023/03/03 10:48:00 UTC
[jira] [Created] (IMPALA-11968) test_event_based_replication fails with timeout
Zoltán Borók-Nagy created IMPALA-11968:
------------------------------------------
Summary: test_event_based_replication fails with timeout
Key: IMPALA-11968
URL: https://issues.apache.org/jira/browse/IMPALA-11968
Project: IMPALA
Issue Type: Bug
Components: Catalog
Reporter: Zoltán Borók-Nagy
Might be related to IMPALA-11352 but the error message is a bit different.
h3. Error Message
{noformat}
metadata/test_event_processing.py:179: in test_event_based_replication self.__run_event_based_replication_tests() metadata/test_event_processing.py:194: in __run_event_based_replication_tests EventProcessorUtils.wait_for_event_processing(self) util/event_processor_utils.py:65: 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 45924 within 10 seconds
{noformat}
h3. Stacktrace
{noformat}
metadata/test_event_processing.py:179: in test_event_based_replication
self.__run_event_based_replication_tests()
metadata/test_event_processing.py:194: in __run_event_based_replication_tests
EventProcessorUtils.wait_for_event_processing(self)
util/event_processor_utils.py:65: 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 45924 within 10 seconds
{noformat}
h3. Standard Error
{noformat}
SET client_identifier=metadata/test_event_processing.py::TestEventProcessing::()::test_event_based_replication;
-- connecting to: localhost:21000
-- 2023-03-02 05:46:47,066 INFO MainThread: Could not connect to ('::1', 21000, 0, 0)
Traceback (most recent call last):
File "/data/jenkins/workspace/impala-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.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-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.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
-- connecting to localhost:21050 with impyla
-- 2023-03-02 05:46:47,067 INFO MainThread: Could not connect to ('::1', 21050, 0, 0)
Traceback (most recent call last):
File "/data/jenkins/workspace/impala-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.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-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.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
-- 2023-03-02 05:46:47,077 INFO MainThread: Closing active operation
-- connecting to localhost:28000 with impyla
-- 2023-03-02 05:46:47,089 INFO MainThread: Closing active operation
-- connecting to localhost:11050 with impyla
-- 2023-03-02 05:46:52,124 INFO MainThread: Waiting until events processor syncs to event id:45924
{noformat}
--
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