Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/4818#issuecomment-76515153
@sryza When cpu scheduling is enabled (ref @tgravescs comment here and in
jira) it must be validated.
Just as we validate memory and while prioritizing based on locality of the
returned resource.
It is a current implementation detail of YARN that it tries to ensure that
response contains resource with adequate cpu and memory (or cpu scheduling is
disabled) - but this could easily change in future.
Ideally, yarn must have returned requested vCores in the response when cpu
scheduling is disabled ... but that is a different issue.
---
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
