Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16620
I'll spend some time today trying to sort out the relative merits of the
fix options; but in the meantime, there's also no good reason for
`TaskSchedulerImpl.rootPool` to be a `var` initialized as `null`, nor any good
reason for `TaskScheduler.rootPool` to be able to produce `null`. Cleaning
that up also makes code in this PR slightly simpler:
https://github.com/markhamstra/spark/commit/e11fe2a9817559492daee03c8c025879dc44d346
---
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]
