Joe McDonnell created IMPALA-12187: -------------------------------------- Summary: TestEventProcessing.test_event_based_replication flaky for truncate table Key: IMPALA-12187 URL: https://issues.apache.org/jira/browse/IMPALA-12187 Project: IMPALA Issue Type: Bug Components: Catalog Affects Versions: Impala 4.3.0 Reporter: Joe McDonnell
There have been a couple Jenkins jobs that have seen a failure on TestEventProcessing.test_event_based_replication() where the test is expecting the truncated table to have zero rows, but instead the table has 100 rows: {noformat} metadata/test_event_processing.py:180: in test_event_based_replication self.__run_event_based_replication_tests() metadata/test_event_processing.py:329: in __run_event_based_replication_tests assert rows_in_part_tbl_target == 0 E assert 100 == 0{noformat} More logs: {noformat} truncate table repl_source_tsmyd.part_tbl; -- 2023-06-02 06:44:19,049 INFO MainThread: Started query 50469ac62856f797:53e74fb400000000 -- 2023-06-02 06:44:41,638 INFO MainThread: Waiting until events processor syncs to event id:32187 -- 2023-06-02 06:44:42,596 DEBUG MainThread: Metric last-synced-event-id has reached the desired value: 32187 -- 2023-06-02 06:44:42,632 DEBUG MainThread: Found 3 impalad/1 statestored/1 catalogd process(es) -- 2023-06-02 06:44:42,648 INFO MainThread: Getting metric: catalog.curr-version from hostname:25000 -- 2023-06-02 06:44:42,651 INFO MainThread: Sleeping 1s before next retry. -- 2023-06-02 06:44:43,653 INFO MainThread: Getting metric: catalog.curr-version from hostname:25000 -- 2023-06-02 06:44:43,669 INFO MainThread: Sleeping 1s before next retry. -- 2023-06-02 06:44:44,670 INFO MainThread: Getting metric: catalog.curr-version from hostname:25000 -- 2023-06-02 06:44:44,674 INFO MainThread: Sleeping 1s before next retry. -- 2023-06-02 06:44:45,676 INFO MainThread: Getting metric: catalog.curr-version from hostname:25000 -- 2023-06-02 06:44:45,679 INFO MainThread: Sleeping 1s before next retry. -- 2023-06-02 06:44:46,680 INFO MainThread: Getting metric: catalog.curr-version from hostname:25000 -- 2023-06-02 06:44:46,683 INFO MainThread: Sleeping 1s before next retry. -- 2023-06-02 06:44:47,685 INFO MainThread: Getting metric: catalog.curr-version from hostname:25000 -- 2023-06-02 06:44:47,688 INFO MainThread: Metric 'catalog.curr-version' has reached desired value: 9771 -- 2023-06-02 06:44:47,688 INFO MainThread: Getting metric: catalog.curr-version from hostname:25001 -- 2023-06-02 06:44:47,691 INFO MainThread: Metric 'catalog.curr-version' has reached desired value: 9771 -- 2023-06-02 06:44:47,691 INFO MainThread: Getting metric: catalog.curr-version from hostname:25002 -- 2023-06-02 06:44:47,694 INFO MainThread: Metric 'catalog.curr-version' has reached desired value: 9771 -- executing against localhost:21000 select count(*) from repl_target_hhkuw.unpart_tbl; -- 2023-06-02 06:44:47,697 INFO MainThread: Started query 6c40644e00cdf143:3be5e75a00000000 -- executing against localhost:21000 select count(*) from repl_target_hhkuw.part_tbl;{noformat} This was seen in a debug core job and a debug erasure coding job. Only for the partitioned table and not the unpartitioned table. This seems like a symptom that doesn't match the existing flakiness for TestEventProcessing.test_event_based_replication(). -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org