hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.
Date Fri, 11 Jul 2014 00:32:04 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058156#comment-14058156

Jian He commented on MAPREDUCE-5910:

patch looks good over all, some comments:
- addOutstandingAllocateRequestOnResync ->addOutstandingRequestsOnResync
- MR_RM_WORKPRESERVING_RESTART_ENABLED flag is not needed any more, given that AM_RESYNC and
AM_SHUTDOWN commands now are sent in different cases.

> MRAppMaster should handle Resync from RM instead of shutting down.
> ------------------------------------------------------------------
>                 Key: MAPREDUCE-5910
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5910
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: applicationmaster
>            Reporter: Rohith
>            Assignee: Rohith
>             Fix For: 2.5.0
>         Attachments: MAPREDUCE-5910.1.patch, MAPREDUCE-5910.2.patch
> The ApplicationMasterService currently sends a resync response to which the AM responds
by shutting down. The MRAppMaster behavior is expected to change to calling resyncing with
the RM. Resync means resetting the allocate RPC sequence number to 0 and the AM should send
its entire outstanding request to the RM. Note that if the AM is making its first allocate
call to the RM then things should proceed like normal without needing a resync. The RM will
return all containers that have completed since the RM last synced with the AM. Some container
completions may be reported more than once.

This message was sent by Atlassian JIRA

View raw message