Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/4818#discussion_r25544439
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -290,8 +290,18 @@ private[yarn] class YarnAllocator(
location: String,
containersToUse: ArrayBuffer[Container],
remaining: ArrayBuffer[Container]): Unit = {
+ // SPARK-6050: certain Yarn configurations return a resource
configuration that doesn't match
+ // the request; for example, capacity scheduler +
DefaultResourceCalculator. Allow users in
+ // those situations to disable resource matching.
+ val matchingResource =
+ if (sparkConf.getBoolean("spark.yarn.container.matchAnyResource",
false)) {
--- End diff --
Sorry I'm still not seeing it. resource is:
Resource.newInstance(executorMemory + memoryOverhead, executorCores)
which is going to be executorCores passed in, which would be for instance 8
if I request 8.
That resource is then passed to amClient.getMatchingRequests which is going
to find requests that have 8 vcores, which isn't what we want because the RM
without cpu scheduling returns ones with 1.
---
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]
