[
https://issues.apache.org/jira/browse/MAPREDUCE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089191#comment-13089191
]
Arun C Murthy commented on MAPREDUCE-2649:
------------------------------------------
Thomas the patch looks fine, I fixed a minor package name problem for
TestAppManager and ran all the tests.
One minor issue: looks like there is no way for the job-client to understand
that it submitted the same app twice since the error is silently lost in
RMAppManager with:
{code}
if (rmContext.getRMApps().putIfAbsent(applicationId, application) !=
null) {
LOG.info("Application with id " + applicationId +
" is already present! Cannot add a duplicate!");
// don't send event through dispatcher as it will be handled by app
already
// present with this id.
application.handle(new RMAppRejectedEvent(applicationId,
"Application with this id is already present! Cannot add a
duplicate!"));
} else {
// ...
{code}
Previously it was caught by the ClientRMService who then threw an exception...
I see no good way around this.
Thoughts?
> 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
