Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/4170#issuecomment-80798498
@elyast Thanks for interesting this PR, which was about resources of cores
and memory. I misunderstood how mesos works specially in memory side, so I
closed this PR. However, I agree with you that executor cores are sometime too
much. @tnachen we cannot adjust memory issue, but, changing executor cores is
meaningful and should fix that executor has same cores with CPUS_PER_TASK
initially. See TODO(pwendell) in MesosSchedulerBackend.scala. I want to fix
this TODO to extract a configuration parameter. What do you think of it?
---
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
