[
https://issues.apache.org/jira/browse/IMPALA-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609651#comment-17609651
]
Joe McDonnell commented on IMPALA-11614:
----------------------------------------
I think it would be better to avoid updating this metric for Ozone.
> TestValidateMetrics.test_metrics_are_zero fails with num-missing-volume-id
> for Ozone
> ------------------------------------------------------------------------------------
>
> Key: IMPALA-11614
> URL: https://issues.apache.org/jira/browse/IMPALA-11614
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 4.2.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Critical
> Labels: broken-build
>
> TestValidateMetrics.test_metrics_are_zero fails for Ozone with
> {code}
> /data/jenkins/workspace/impala-private-ozone-parameterized/repos/Impala/tests/common/impala_service.py:210:
> in __metric_timeout_assert
> assert 0, assert_string
> E AssertionError: Metric impala-server.scan-ranges.num-missing-volume-id
> did not reach value 0 in 60s.
> {code}
> This passed at one point:
> https://master-03.jenkins.cloudera.com/view/Impala/view/Evergreen-asf-master/job/impala-asf-master-core-ozone/7/
> with commit 17ec3a85c7e3733dacb08a9fcca83fff5ec75102 succeeded. I suspect it
> started failing as a result of 79e474d310 (IMPALA-10213) because now most
> tests see Ozone datanodes as local rather than remote.
--
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
