[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077192#comment-14077192 ]
Junping Du commented on YARN-2209: ---------------------------------- bq. I think users are expected to handle two types of exceptions YarnException and IOException. In that sense, this is equivalent to throwing a new type of exception which should be fine? No. The customized AM code could get RESYNC from response previously (like what we original do in AMRMClient) to handle AM re-registering case. Now, it cannot get this RESYNC so could failed to re-registering to restarted RM. Do I miss anything here? > Replace AM resync/shutdown command with corresponding exceptions > ---------------------------------------------------------------- > > Key: YARN-2209 > URL: https://issues.apache.org/jira/browse/YARN-2209 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Jian He > Assignee: Jian He > Attachments: YARN-2209.1.patch, YARN-2209.2.patch, YARN-2209.3.patch, > YARN-2209.4.patch, YARN-2209.5.patch > > > YARN-1365 introduced an ApplicationMasterNotRegisteredException to indicate > application to re-register on RM restart. we should do the same for > AMS#allocate call also. -- This message was sent by Atlassian JIRA (v6.2#6252)