Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
Impala 4.2.0
-
None
-
ghx-label-13
Description
The test fails with the same timout symptom on all builds that are not run on straight HDFS storage: S3 and EC (erasure coding) builds are both affected.
Stack trace:
custom_cluster.test_scheduler_locality.TestSchedulerLocality.test_local_assignment[protocol: beeswax | exec_option: {'test_replan': 1, 'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0, 'disable_codegen': False, 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format: text/none]
custom_cluster/test_scheduler_locality.py:41: in test_local_assignment
allow_greater=True)
common/impala_service.py:143: in wait_for_metric_value
self.__metric_timeout_assert(metric_name, expected_value, timeout)
common/impala_service.py:210: in __metric_timeout_assert
assert 0, assert_string
E AssertionError: Metric simple-scheduler.local-assignments.total did not reach value 1 in 10s.
E Dumping debug webpages in JSON format...
E Dumped memz JSON to $IMPALA_HOME/logs/metric_timeout_diags_20220909_09:15:50/json/memz.json
E Dumped metrics JSON to $IMPALA_HOME/logs/metric_timeout_diags_20220909_09:15:50/json/metrics.json
E Dumped queries JSON to $IMPALA_HOME/logs/metric_timeout_diags_20220909_09:15:50/json/queries.json
E Dumped sessions JSON to $IMPALA_HOME/logs/metric_timeout_diags_20220909_09:15:50/json/sessions.json
E Dumped threadz JSON to $IMPALA_HOME/logs/metric_timeout_diags_20220909_09:15:50/json/threadz.json
E Dumped rpcz JSON to $IMPALA_HOME/logs/metric_timeout_diags_20220909_09:15:50/json/rpcz.json
E Dumping minidumps for impalads/catalogds...
E Dumped minidump for Impalad PID 16962
E Dumped minidump for Catalogd PID 16907