You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2013/11/07 08:01:29 UTC

[jira] [Updated] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

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

Rohith Sharma K S updated YARN-1366:
------------------------------------

    Attachment: YARN-1366.patch

   Correct me If am wrong, I have prepared initial patch and attached the same. RM should differentiate Resync and Shutdown command.
Please review whether this will fullfill expectations mentioned in JIra.



> ApplicationMasterService should Resync with the AM upon allocate call after restart
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-1366
>                 URL: https://issues.apache.org/jira/browse/YARN-1366
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Bikas Saha
>         Attachments: YARN-1366.patch
>
>
> The ApplicationMasterService currently sends a resync response to which the AM responds by shutting down. The AM 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.1#6144)