[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith updated YARN-1366: ------------------------- Attachment: YARN-1366.4.patch Attached updated patch that address Anubhav's all comments. This patch contains only YarnClient changes. The changes are 1. Added a test that covers the scenario for functionalities. 2. Added core-site.xml for test with disabling ip based check. 3. modified yarn-client pom.xml for getting yarn-common-test in test classpath. I am not changing status for "Patch Available" since test require patch of Yarn-1365. > AM should implement Resync with the ApplicationMasterService instead of > shutting down > ------------------------------------------------------------------------------------- > > Key: YARN-1366 > URL: https://issues.apache.org/jira/browse/YARN-1366 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Bikas Saha > Assignee: Rohith > Attachments: YARN-1366.1.patch, YARN-1366.2.patch, YARN-1366.3.patch, > YARN-1366.4.patch, YARN-1366.patch, YARN-1366.prototype.patch, > YARN-1366.prototype.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.2#6252)