From yarn-issues-return-167813-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon May 20 12:49:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 42E1B180627 for ; Mon, 20 May 2019 14:49:04 +0200 (CEST) Received: (qmail 90225 invoked by uid 500); 20 May 2019 12:49:02 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 90118 invoked by uid 99); 20 May 2019 12:49:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2019 12:49:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 41506E299F for ; Mon, 20 May 2019 12:49:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7E9F42581C for ; Mon, 20 May 2019 12:49:00 +0000 (UTC) Date: Mon, 20 May 2019 12:49:00 +0000 (UTC) From: "Tao Yang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-9567) Add diagnostics for outstanding resource requests on app attempts page MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tao Yang created YARN-9567: ------------------------------ Summary: Add diagnostics for outstanding resource requests on = app attempts page Key: YARN-9567 URL: https://issues.apache.org/jira/browse/YARN-9567 Project: Hadoop YARN Issue Type: Sub-task Components: capacityscheduler Reporter: Tao Yang Assignee: Tao Yang Attachments: no_diagnostic_at_first.png, show_diagnostics_after_re= questing_app_activities_REST_API.png Currently on app attempt page we can see=C2=A0outstanding resource requests= , it will be helpful for users to know why if we can join diagnostics=C2=A0= of this app=C2=A0with these.=C2=A0 Discussed with [~cheersyang], we can=C2=A0passively load diagnostics from c= ache of completed app activities=C2=A0instead of=C2=A0actively triggering w= hich may=C2=A0bring uncontrollable risk. For example: (1) At first=C2=A0we can see=C2=A0no diagnostic in cache if app activities = not triggered below the outstanding requests. !no_diagnostic_at_first.png! (2) After requesting the application activities REST API, we can see diagno= stics=C2=A0now. =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org