Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 8860011896 for ; Mon, 21 Jul 2014 17:02:49 +0000 (UTC) Received: (qmail 37727 invoked by uid 500); 21 Jul 2014 17:02:42 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 37625 invoked by uid 500); 21 Jul 2014 17:02:42 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 37395 invoked by uid 99); 21 Jul 2014 17:02:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jul 2014 17:02:42 +0000 Date: Mon, 21 Jul 2014 17:02:42 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (MAPREDUCE-536) The information displayed by the capacity scheduler can be improved MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved MAPREDUCE-536. ---------------------------------------- Resolution: Incomplete Closing this as stale given the UI is completely different now. > The information displayed by the capacity scheduler can be improved > ------------------------------------------------------------------- > > Key: MAPREDUCE-536 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-536 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Reporter: Amar Kamat > > As of now the information displayed by the capacity scheduler is sequential. Following are some ways I think we can improve the display > - It would make more sense if we display it as a table where comparing the information across queues would be easy. Something like > || ||Queue1||Queue2|| > |guaranteed cap|75%|25%| > - Along with {{Reclaim Time Limit}} there should be a hint/info about how much time capacity-scheduler thinks it will take to reclaim i.e it would be nice to know the time left to reclaim. > || ||Queue1||Queue2|| > |Reclaim time limit|300000|300000| > |Time left to reclaim|500|120000| > - All the timing information should have units specified. {{Reclaim time limit : 300000}} doesnt give any information what the unit is. > || ||Queue1||Queue2|| > |Reclaim time limit|5 mins|5 mins| > |Time left to reclaim|500 msec| 2 mins| > - Common information like disclaimers can move out of the table/display to a common place. > - Showing guaranteed and (actual) running tasks doesnt convey much info. It should be shown together. Something like > || ||Queue1||Queue2|| > |running/guaranteed maps|1/16|15/16| > - We can also improve/enhance the way boolean information is displayed using ticks and crosses. Something like > || ||Queue1||Queue2|| > |Priorities|(/)|(x)| -- This message was sent by Atlassian JIRA (v6.2#6252)