Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/15326
+1 to Mark's suggestion about putting the behavior in Pool::addSchedulable,
so that it works across all Schedulables.
I'm less convinced about maintaining the existing behavior where the last
added pool wins. I think people usually expect first-wins behavior for these
things (e.g., that's the case for Java classpath issues), and the code is also
simpler for that approach. Given that this should be affecting pretty few
people (and there's now a warning logged), I think this would be fine to change.
---
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
