You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2022/09/27 17:03:00 UTC

[jira] [Resolved] (IMPALA-11614) TestValidateMetrics.test_metrics_are_zero fails with num-missing-volume-id for Ozone

     [ https://issues.apache.org/jira/browse/IMPALA-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Smith resolved IMPALA-11614.
------------------------------------
    Resolution: Fixed

> 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
>             Fix For: Impala 4.2.0
>
>
> 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)