Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 Mar 2017 17:18:42 +0000 (UTC)
From: "Roni Burd (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13056732.1489684691000.39895.1489684722114@Atlassian.JIRA>
In-Reply-To: <JIRA.13056732.1489684691000@Atlassian.JIRA>
References: <JIRA.13056732.1489684691000@Atlassian.JIRA> <JIRA.13056732.1489684691984@jira-lw-us.apache.org>
Subject: [jira] [Created] (YARN-6350) Add JMX counters to track locality
 matching (node, rack, off_switch)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Mar 2017 17:18:47 -0000

Roni Burd created YARN-6350:
-------------------------------

             Summary: Add JMX counters to track locality matching (node, rack, off_switch)
                 Key: YARN-6350
                 URL: https://issues.apache.org/jira/browse/YARN-6350
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: metrics, yarn
            Reporter: Roni Burd
            Priority: Minor


When using realxLocality=true, it would be nice to have metrics to see how well the RM is fulfilling the requests. This helps to tune the relaxLocality params and compare the behavior.

The proposal is to have 3 metrics exposed via JMX
-node matching % 
-rack matching %
-off_switch matching % 

Each one represents the matching that occurred compared to the total matched asked. 

The metrics would have to take into account the type of request (e.g node, ANY, etc)


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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