Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3486#discussion_r21563321
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/SparkListener.scala ---
@@ -84,6 +86,14 @@ case class SparkListenerBlockManagerRemoved(time: Long,
blockManagerId: BlockMan
@DeveloperApi
case class SparkListenerUnpersistRDD(rddId: Int) extends SparkListenerEvent
+@DeveloperApi
+case class SparkListenerExecutorAdded(executorId: String, executorInfo :
ExecutorInfo)
+ extends SparkListenerEvent
+
+@DeveloperApi
+case class SparkListenerExecutorRemoved(executorId: String, executorInfo :
ExecutorInfo)
+ extends SparkListenerEvent
+
--- End diff --
Hm I'm not so sure about introducing these new events. We already have a
`BlockManager*` and there is actually a one-to-one corresponding between BMs
and Executors (unfortunately). Meaning, every time `onExecutorAdded` is called
`onBlockManagerAdded` will also be called.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
