hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2649) MR279: Fate of finished Applications on RM
Date Fri, 19 Aug 2011 15:30:27 GMT

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

Thomas Graves updated MAPREDUCE-2649:
-------------------------------------

    Attachment: MAPREDUCE-2649-v6.patch

Updates to have RMAppManager.

> MR279: Fate of finished Applications on RM
> ------------------------------------------
>
>                 Key: MAPREDUCE-2649
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2649
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2649-patch-mr279.txt, MAPREDUCE-2649-v2.patch, MAPREDUCE-2649-v3.patch,
MAPREDUCE-2649-v4.patch, MAPREDUCE-2649-v5.patch, MAPREDUCE-2649-v6.patch
>
>
> Today RM keeps the references of finished application for ever. Though this is not sustainable
long term, it keeps
> the user experience saner. Users can revisit RM UI and check the status of their apps.
> We need to think of purging old references yet keeping the UX sane.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message