[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746518#comment-16746518
]
Michael Brown commented on IMPALA-8064:
---------------------------------------
[~janulatha] This is still happening on master in a downstream ASAN build+test.
I confirmed it was at a Git hash that had the fix above and of course the
correct {{RUNTIME_FILTER_WAIT_TIME_MS}} is evident.
{noformat}
query_test/test_runtime_filters.py:114: in test_min_max_filters
test_file_vars={'$RUNTIME_FILTER_WAIT_TIME_MS': str(WAIT_TIME_MS)})
common/impala_test_suite.py:518: in run_test_case
update_section=pytest.config.option.update_results)
common/test_result_verifier.py:612: in verify_runtime_profile
% (function, field, expected_value, actual_value, actual))
E AssertionError: Aggregation of SUM over ProbeRows did not match expected
results.
E EXPECTED VALUE:
E 643
E
E ACTUAL VALUE:
E 661
E
{noformat}
The query in question:
{noformat}
USE functional_kudu;
SET RUNTIME_FILTER_WAIT_TIME_MS=100000;
select STRAIGHT_JOIN count(*) from decimal_rtf_tbl a
join [BROADCAST] decimal_rtf_tiny_tbl b
where a.d38_38 = b.d38_38 and b.d38_38 != 0;
{noformat}
Snippets from the profile which I'll upload in full show that 2/3 scan nodes
did not receive the runtime filter in time.
{noformat}
Instance 2b4a14d9933eb108:7565b86500000006
(host=downstream-jenkins-host:22001):(Total: 1m47s, non-child: 3.999ms, %
non-child: 0.00%)
HASH_JOIN_NODE (id=2):(Total: 172.996ms, non-child: 9.999ms, %
non-child: 5.78%)
Runtime filters: 1 of 1 Runtime Filter Published
KUDU_SCAN_NODE (id=0):(Total: 162.996ms, non-child: 162.996ms, %
non-child: 100.00%)
Runtime filters: All filters arrived. Waited 0
Instance 2b4a14d9933eb108:7565b86500000004
(host=downstream-jenkins-host:22000):(Total: 1m42s, non-child: 0.000ns, %
non-child: 0.00%)
HASH_JOIN_NODE (id=2):(Total: 13s819ms, non-child: 25.999ms, %
non-child: 0.10%)
Runtime filters: 1 of 1 Runtime Filter Published
KUDU_SCAN_NODE (id=0):(Total: 11s359ms, non-child: 11s359ms, %
non-child: 100.00%)
Runtime filters: Not all filters arrived (arrived: [], missing [1]),
waited for 11s337ms
Instance 2b4a14d9933eb108:7565b86500000005
(host=downstream-jenkins-host:22002):(Total: 1m42s, non-child: 0.000ns, %
non-child: 0.00%)
HASH_JOIN_NODE (id=2):(Total: 39s251ms, non-child: 6.999ms, %
non-child: 0.01%)
Runtime filters: 1 of 1 Runtime Filter Published
KUDU_SCAN_NODE (id=0):(Total: 36s812ms, non-child: 36s812ms, %
non-child: 100.00%)
Runtime filters: Not all filters arrived (arrived: [], missing [1]),
waited for 36s768ms
{noformat}
> test_min_max_filters is flaky
> ------------------------------
>
> Key: IMPALA-8064
> URL: https://issues.apache.org/jira/browse/IMPALA-8064
> Project: IMPALA
> Issue Type: Bug
> Reporter: Pooja Nilangekar
> Assignee: Janaki Lahorani
> Priority: Blocker
> Labels: broken-build, flaky-test
>
> The following configuration of the test_min_max_filters:
> {code:java}
> query_test.test_runtime_filters.TestMinMaxFilters.test_min_max_filters[protocol:
> beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
> 'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
> 'abort_on_error': 1, 'debug_action': None, 'exec_single_node_rows_threshold':
> 0} | table_format: kudu/none]{code}
> It produces a higher aggregation of sum over the proberows than expected:
> {code:java}
> query_test/test_runtime_filters.py:113: in test_min_max_filters
> self.run_test_case('QueryTest/min_max_filters', vector)
> common/impala_test_suite.py:518: in run_test_case
> update_section=pytest.config.option.update_results)
> common/test_result_verifier.py:612: in verify_runtime_profile %
> (function, field, expected_value, actual_value, actual))
> E AssertionError: Aggregation of SUM over ProbeRows did not match expected
> results.
> E EXPECTED VALUE: E 619
> E ACTUAL VALUE: E 652
> {code}
> This test was introduced in the patch for IMPALA-6533. The failure occurred
> during an ASAN build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
