Github user lirui-intel commented on the issue:
https://github.com/apache/spark/pull/16376
The change looks good to me, although I still want to make sure I
understand it correctly. Before the change, a locality level is invalid if it
has delay=0. The patch changes that and makes such locality level valid too. So
during scheduling, it gives us a chance to try the smaller levels first, e.g.
PROCESS_LOCAL, NODE_LOCAL, otherwise we'll just schedule the task to any
executors available. And meanwhile, since the wait time for the smaller levels
are 0, we'll quickly fall back to ANY if a satisfying executor is not
available. So that the delay=0 is still enforced. Is this correct?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
