You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Rohith (JIRA)" <ji...@apache.org> on 2014/07/01 08:00:34 UTC

[jira] [Updated] (MAPREDUCE-5910) MRAppMaster should handle Resync from RM instead of shutting down.

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

Rohith updated MAPREDUCE-5910:
------------------------------

    Status: Open  (was: Patch Available)

cancelling the patch to fix the findbug error

> 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
>
>
> 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
(v6.2#6252)