Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/4818#discussion_r25545356
--- 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 --
Oh, sorry I see now. I was reading it backwards and thinking it was
matching what was actually allocated.
So I guess the question is whether we want the default of this to be true
so that its backwards compatible. Otherwise the behavior changes for anyone
running now that upgrades.
---
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]
