Github user zhzhan commented on the issue:
https://github.com/apache/spark/pull/15218
@mridulm Thanks for the comments. Your concern regarding the locality is
right. The patch does not change this behavior, which takes priority of
locality preference. But if multiple executors satisfying the locality
restriction, the policy will be applied. In our production pipeline, we do see
a big gain with respect to reserved cpu resources when dynamic allocation is
enabled.
@kayousterhout Would you like take a look and provide your comments?
---
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]
