[
https://issues.apache.org/jira/browse/SPARK-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031843#comment-15031843
]
Thomas Graves commented on SPARK-4117:
--------------------------------------
[~devaraj.k] thanks for explaining. Sounds good on
ApplicationMasterNotRegisteredException since the AMRMClientImpl is handling
it.
For ApplicationAttemptNotFoundException, you hit one of the places that
allocate is called and that is on the first registration. There is another one
in the launchReporterThread that regularly gets called after starting. This is
the one that catches exceptions and will wait for a number of failures before
finally exits. So if ApplicationAttemptNotFoundException is sent anytime after
the application is running it will hit that logic. I don't think its that big
of an issue since it will eventually exit, it could just take a little longer.
It looks like the only cases that should be thrown is if we have already
unregistered or something weird happened on RM Where it lost the application.
> Spark on Yarn handle AM being told command from RM
> --------------------------------------------------
>
> Key: SPARK-4117
> URL: https://issues.apache.org/jira/browse/SPARK-4117
> Project: Spark
> Issue Type: Improvement
> Components: YARN
> Affects Versions: 1.2.0
> Reporter: Thomas Graves
>
> In the allocateResponse from the RM it can send commands that the AM should
> follow. for instance AM_RESYNC and AM_SHUTDOWN. We should add support for
> those.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
