You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2017/08/14 04:53:00 UTC
[jira] [Resolved] (IMPALA-467) Builds intermittently fail due to
problems getting the volume id metadata
[ https://issues.apache.org/jira/browse/IMPALA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-467.
----------------------------------
Resolution: Cannot Reproduce
> Builds intermittently fail due to problems getting the volume id metadata
> -------------------------------------------------------------------------
>
> Key: IMPALA-467
> URL: https://issues.apache.org/jira/browse/IMPALA-467
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 1.1
> Reporter: Lenni Kuff
> Assignee: Ishaan Joshi
> Priority: Critical
> Labels: test-infra
>
> Builds intermittently fail due to problems getting the volume id metadata. This shows up when we check the 'impala-server.scan-ranges.num-missing-volume-id' metric when performing post-test run metric validation.
> {code}
> verifiers/test_verify_metrics.py:59: in __assert_metric_value
> > (metric_name, actual_value, expected_value)
> E AssertionError: Metric 'impala-server.scan-ranges.num-missing-volume-id' value is: 29 Expected: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)