hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7136) TestMRAppMetrics should shutdown DefaultMetricsSystem after completion
Date Tue, 11 Sep 2018 20:01:00 GMT

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

Jason Lowe commented on MAPREDUCE-7136:
---------------------------------------

I would recommend opening a single ticket per maven project or even per JIRA project if it's
not too huge of a patch to address these.  I agree fixing these one at a time is going to
be too much overhead.  Be sure to call out that this is a fix for JVM reuse tests (e.g.: run
via IDE) and not a test failure seen by running surefire, or people may get confused since
they cannot reproduce it.

> TestMRAppMetrics should shutdown DefaultMetricsSystem after completion
> ----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-7136
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7136
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Oleksandr Shevchenko
>            Assignee: Oleksandr Shevchenko
>            Priority: Minor
>             Fix For: 3.2.0
>
>         Attachments: MAPREDUCE-7136.001.patch, image-2018-09-10-14-39-57-992.png
>
>
> TestMRAppMetrics should invoke shutdown method in DefaultMetricsSystem after completion.
Since it can lead to failing other tests. For example, TestRMContainerAllocator#testReportedAppProgress
fails when run after TestMRAppMetrics#testNames with the following error:
> {noformat}
> org.apache.hadoop.metrics2.MetricsException: Metrics source MRAppMetrics already exists!
> {noformat}
> !image-2018-09-10-14-39-57-992.png!
> We do not catch this on the trunk since the test TestRMContainerAllocator#testUnsupportedMapContainerRequirement
run first and "DefaultMetricsSystem.shutdown();" invokes after completion. But since JUnit
does not guarantee the order of the tests we should fix it. 
>  Also, this is affected by previous versions which run testReportedAppProgress first
(I faced it on 2.7.0 version). And reproduced on the trunk.



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

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


Mime
View raw message