[
https://issues.apache.org/jira/browse/YARN-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990875#comment-16990875
]
Manikandan R edited comment on YARN-4901 at 12/8/19 3:09 PM:
-------------------------------------------------------------
Backporting to branch 3.2 mainly to address
https://issues.apache.org/jira/browse/YARN-10012?focusedCommentId=16990109&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16990109
was (Author: maniraj...@gmail.com):
Backporting to branch 3.2.
> QueueMetrics needs to be cleared before MockRM is initialized
> -------------------------------------------------------------
>
> Key: YARN-4901
> URL: https://issues.apache.org/jira/browse/YARN-4901
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Reporter: Daniel Templeton
> Assignee: Peter Bacsko
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-4901-001.patch, YARN-4901-branch-3.2.002.patch
>
>
> The {{ResourceManager}} rightly assumes that when it starts, it's starting
> from naught. The {{MockRM}}, however, violates that assumption. For
> example, in {{TestNMReconnect}}, each test method creates a new {{MockRM}}
> instance. The {{QueueMetrics.queueMetrics}} field is static, which means
> that when multiple {{MockRM}} instances are created, the {{QueueMetrics}}
> bleed over. Having the MockRM clear the {{QueueMetrics}} when it starts
> should resolve the issue. I haven't looked yet at scope to see how hard easy
> that is to do.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
