Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4B5761139D for ; Fri, 22 Aug 2014 19:58:13 +0000 (UTC) Received: (qmail 87365 invoked by uid 500); 22 Aug 2014 19:58:13 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 87318 invoked by uid 500); 22 Aug 2014 19:58:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 87305 invoked by uid 99); 22 Aug 2014 19:58:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2014 19:58:13 +0000 Date: Fri, 22 Aug 2014 19:58:13 +0000 (UTC) From: "Renan DelValle (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-2408) Resource Request REST API for YARN MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-2408?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Renan DelValle updated YARN-2408: --------------------------------- Attachment: (was: YARN-2408-2.patch) > Resource Request REST API for YARN > ---------------------------------- > > Key: YARN-2408 > URL: https://issues.apache.org/jira/browse/YARN-2408 > Project: Hadoop YARN > Issue Type: New Feature > Components: webapp > Reporter: Renan DelValle > Labels: features > Attachments: YARN-2408-3.patch > > > I=E2=80=99m proposing a new REST API for YARN which exposes a snapshot of= the Resource Requests that exist inside of the Scheduler. My motivation be= hind this new feature is to allow external software to monitor the amount o= f resources being requested to gain more insightful information into cluste= r usage than is already provided. The API can also be used by external soft= ware to detect a starved application and alert the appropriate users and/or= sys admin so that the problem may be remedied. > Here is the proposed API: > {code:xml} > > 96256 > 94 > > application_ > appattempt_ > default > 96256 > 94 > 3 > > > 1024 > 1 > /default-rack > 94 > true > 20 > > > 1024 > 1 > * > 94 > true > 20 > > > 1024 > 1 > master > 94 > true > 20 > > > > > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)