Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 B77089B66 for ; Thu, 14 Jun 2012 20:38:43 +0000 (UTC) Received: (qmail 36940 invoked by uid 500); 14 Jun 2012 20:38:43 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 36851 invoked by uid 500); 14 Jun 2012 20:38:43 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 36572 invoked by uid 99); 14 Jun 2012 20:38:42 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2012 20:38:42 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id BA422141663 for ; Thu, 14 Jun 2012 20:38:42 +0000 (UTC) Date: Thu, 14 Jun 2012 20:38:42 +0000 (UTC) From: "Lewis John McGibbney (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1888609175.16923.1339706322764.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HADOOP-8510) Implement auto-refresh for dsfhealth.jsp and jobtracker.jsp MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Lewis John McGibbney created HADOOP-8510: -------------------------------------------- Summary: Implement auto-refresh for dsfhealth.jsp and jobtracker.jsp Key: HADOOP-8510 URL: https://issues.apache.org/jira/browse/HADOOP-8510 Project: Hadoop Common Issue Type: Improvement Affects Versions: 1.0.1 Reporter: Lewis John McGibbney Priority: Trivial A simple auto refresh switch would be nice from within the webapp. I am pretty confused by which version to patch, I've looked in trunk and find myself even more confused. If someone would be kind enough to point out where I can check out code and patch to include this issue then I'll happily submit the trivial patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira