Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/7839#discussion_r36129114
--- Diff:
network/yarn/src/main/java/org/apache/spark/network/yarn/YarnShuffleService.java
---
@@ -100,11 +119,33 @@ private boolean isAuthenticationEnabled() {
*/
@Override
protected void serviceInit(Configuration conf) {
+
+ // In case this NM was killed while there were running spark
applications, we need to restore
+ // lost state for the existing executors. We look for an existing
file in the NM's local dirs.
+ // If we don't find one, then we choose a file to use to save the
state next time. However, we
+ // do *not* immediately register all the executors in that file, just
in case the application
+ // was terminated while the NM was restarting. We wait until yarn
tells the service about the
+ // app again via #initializeApplication, so we know its still running.
That is important
+ // for preventing a leak where the app data would stick around
*forever*. This does leave
+ // a small race -- if the NM restarts *again*, after only some of the
existing apps have been
+ // re-registered, their info will be lost.
--- End diff --
The NodeManager/RM should handle is any applications were deleting while it
was down and send the stopApplication. It normally does this when the NM
re-registers with the RM.
I think I would error on leaking a couple then losing information.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
