Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 13 Oct 2011 10:25:11 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <398904872.8557.1318501511981.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <305916859.5783.1318441871899.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3174) app master UI goes away when app
 finishes - not very user friendly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated MAPREDUCE-3174:
-----------------------------------------------

    Priority: Blocker  (was: Minor)

Thomas, thanks for reporting.

This is more than a minor annoyance, we need to fix this before the release. Bumping its status to a blocker.

Regarding possible solutions, we can have a Http-proxy at RM like Todd mentioned or we could have a simple IFrame/JS in the AM web-UI which periodically checks the liveness of AM UI and redirects to JobHistory when AM exits.
                
> app master UI goes away when app finishes - not very user friendly
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3174
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3174
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Priority: Blocker
>
> A user can go to the application master UI to see the stats on the app, but as soon as the app finishes that UI goes away and user is left with nothing.  A redirect to history server or similar would be much better.

--
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