[
https://issues.apache.org/jira/browse/IMPALA-14098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954425#comment-17954425
]
ASF subversion and git services commented on IMPALA-14098:
----------------------------------------------------------
Commit 063b90c433e64a5ff881d757d7eca0f2c4521f8f in impala's branch
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=063b90c43 ]
IMPALA-14098: Fix test_pool_config_change_while_queued
test_pool_config_change_while_queued has been failing for not finding
admission-controller.pool-max-query-mem-limit.root.invalidTestPool
metric reaching 0. This patch increase the mem_limit config in
ResourcePoolConfig.__wait_for_impala_to_pickup_config_change() from 10G
to 20G to ensure that the trigger query is always rejected and refresh
the pool config.
Testing:
Loop the test 10 times in exhaustive mode and pass them all.
Change-Id: If903840f81d54d58947fe596ecc0c86e6a234b60
Reviewed-on: http://gerrit.cloudera.org:8080/22946
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Deflake test_pool_config_change_while_queued
> --------------------------------------------
>
> Key: IMPALA-14098
> URL: https://issues.apache.org/jira/browse/IMPALA-14098
> Project: IMPALA
> Issue Type: Test
> Reporter: Riza Suminto
> Assignee: Riza Suminto
> Priority: Major
>
> test_pool_config_change_while_queued has been failing for not finding
> admission-controller.pool-max-query-mem-limit.root.invalidTestPool metric
> reaching 0. The high MEM_LIMIT that suppose to refresh the pool config does
> not seem to be effective anymore and require some increment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
