Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6352#issuecomment-104947471
Actually, it looks like we end up calling `clearCacheLocs()` when
submitting a new job, so the change described above probably doesn't make a
difference. To be safe, though, and to eliminate the `return`, let's go ahead
and move it into the `cacheLocs`-updating block. Once we do that, I think this
will be good to go, but I'll probably pull in a scheduler maintainer for a
final spot-check / review.
---
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]
