Github user davies commented on the pull request:
https://github.com/apache/spark/pull/3779#issuecomment-72598196
For any resource, it will try from the highest locality. TaskSetManager
checks the current lowest locality level's wait is non-zero to determine the
allowed lowest locality level. If it's zero, then TaskSetManager should assign
the possible highest task for the resource, without any waiting. I think it
make sense.
There are some logic are perf related, such as the index of task is removed
from `list` lazily (only scanned once). Others (using locality levels to index
into parallel arrays) are out of this PR's scope.
@rxin Could you also help to look at this PR?
---
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]
