hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4901) MockRM should clear the QueueMetrics when it starts
Date Wed, 06 Apr 2016 07:07:25 GMT

    [ https://issues.apache.org/jira/browse/YARN-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227867#comment-15227867

Karthik Kambatla commented on YARN-4901:

TestNMReconnect fails with FairScheduler because of this. 

> MockRM should clear the QueueMetrics when it starts
> ---------------------------------------------------
>                 Key: YARN-4901
>                 URL: https://issues.apache.org/jira/browse/YARN-4901
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
> 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

View raw message