Github user squito commented on the issue:
https://github.com/apache/spark/pull/21068
I think Tom makes a good case for why this should live in the YarnAllocator
as you have it.
I also don't think you need to worry about creating an abstract class yet,
that refactoring can be done when another cluster manager tries to share some
code ... it would just be helpful to keep that use in mind.
also I filed https://issues.apache.org/jira/browse/SPARK-24016 for updating
the task-based node blacklist even with static allocation
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
