hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15442) ITestS3AMetrics.testMetricsRegister can't know metrics source's name
Date Tue, 15 May 2018 15:20:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475996#comment-16475996
] 

Hudson commented on HADOOP-15442:
---------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #14200 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14200/])
HADOOP-15442. ITestS3AMetrics.testMetricsRegister can't know metrics (stevel: rev b6708374692e6c4d786e2f3f1f45cc7aa1e4e88f)
* (edit) hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInstrumentation.java
* (edit) hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3AMetrics.java


> ITestS3AMetrics.testMetricsRegister can't know metrics source's name
> --------------------------------------------------------------------
>
>                 Key: HADOOP-15442
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15442
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3, metrics
>    Affects Versions: 3.1.0
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Major
>             Fix For: 3.1.1
>
>         Attachments: HADOOP-15442.001.patch
>
>
> I've seen this test fail a bunch lately - mainly when the tests are all run (i.e. not
individually) but not in parallel, it seems. If you dump out the sources when it fails, you
see:
> * The sources are numbered in the hundreds, so it's very unlikely that this actually
gets the first one.
> * The sources are numbered twice. There was logic to have the first one not be numbered,
but that got messed up and now all sources are numbered twice, but the first one is only number
once.
> We could just remove the bad assertion, but then we're only testing the registry and
not anything else about the way metrics flow all the way through the whole system. Worth it
to fix the failing test, I think - knowing the source gets registered doesn't add a whole
lot of value toward end-to-end metrics testing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message