Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6546#issuecomment-107753794
> The problem of a new SparkListener is "adding an Executor" may happen
before "adding the new
> SparkListener to SparkContext". So the new SparkListener may miss some
messages before adding
> itself to SparkContext. JobProgressListener is added as early as possible
so that it won't miss any
> message.
hmm, good point. You can make sure listeners are added immediately with
[`spark.extraListeners`](https://github.com/apache/spark/blob/90c606925e7ec8f65f28e2290a0048f64af8c6a6/core/src/main/scala/org/apache/spark/SparkContext.scala#L1945),
but that is admittedly a pain since you don't get a handle on our listener, so
you need some to communicate via some global variable. I guess I don't feel
strongly either way then.
---
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]
