Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/4688#discussion_r28961383
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -121,8 +125,7 @@ class CoarseGrainedSchedulerBackend(scheduler:
TaskSchedulerImpl, val rpcEnv: Rp
context.reply(RegisterExecutorFailed("Duplicate executor ID: " +
executorId))
} else {
logInfo("Registered executor: " + executorRef + " with ID " +
executorId)
- context.reply(RegisteredExecutor)
-
+ context.reply(RegisteredExecutor(latestTokens))
--- End diff --
so if an executor dies, and by this I assume the entire container dies, the
AM would relaunch a new container and when it does this I would have expected
it to send the new credentials it acquired by doing the loginfromkeytab. See
the ExecutorRunnable.startContainer where it writes the credentials into the
launch context.
Is that not happening? Or is there a case I'm not thinking of?
---
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
