Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/11129#issuecomment-217520612
It's actually being fixed right now in Hadoop 2.8, which will take a while
to surface.
[YARN-4925](https://issues.apache.org/jira/browse/YARN-4925).
Looking at the patch, all Bibin is doing is cutting that validation check
out from the container request submission...it's up to the scheduler how it
handles things at that point. Presumably (hopefully) it does the right thing.
If the patch goes in to spark, then eventually, there may be benefits in
pulling it. If it goes in now, it stops things breaking today.
This is a tough call...nobody wants to add another switch for this do they?
(now, maximally devious would be to catch the exception and downgrade, but
that's both hard to test and inevitably brittle in some way)
---
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]
