[
https://issues.apache.org/jira/browse/MAPREDUCE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089197#comment-13089197
]
Thomas Graves commented on MAPREDUCE-2649:
------------------------------------------
To be more clear its in the patch already..
+ ApplicationId applicationId = submissionContext.getApplicationId();
+ if (rmContext.getRMApps().get(applicationId) != null) {
throw new IOException("Application with id " + applicationId
+ " is already present! Cannot add a duplicate!");
}
> 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, MAPREDUCE-2649-v7.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
