Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/21589
@mridulm scheduler pools could also make the cluster-wide resource numbers
not very meaningful. I don't think the maxShare work has been merged yet (kind
of a stalled TODO on an open PR, IIRC), but once that is in, it's not terribly
useful to know, e.g., that there are 5 million cores in the cluster if your Job
is running in a scheduler pool that is restricted to using far fewer CPUs via
the pool's maxShares.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
