Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/5063#issuecomment-84712739
I see. So frameworkCores isn't ideal because "framework" already has a
meaning in the Mesos world. Also, "executor" already has some inherent
ambiguity because Mesos uses it differently than Spark. So
`spark.mesos.executor.cores` sounds reasonable to me.
I'm still somewhat confused by the need for such a property (and this might
still be stemming from me not understanding about how Spark Mesos integration
works). If my understanding is correct, the cores included in
`spark.mesos.executor.cores` are never made available to tasks. If that's the
case, when would the Mesos executor ever need more than a single core? Does
anything the executor is doing require much CPU?
---
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]
