Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9095#issuecomment-147667700
@srowen , not sure what exactly you mean?
From what I know in `CoarseGrainedSchedulerBackend`, it will manage the
executors with cores available, this number of cores is reported by executor
when get launched and registered in driver. And executor gets the number of
cores through argument specified in launching command, if we specify the wrong
cores, driver will also get the wrong cores, that will be different from what
we see in the cluster manager's aspect.
---
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]
