Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/800#issuecomment-43354675
Just a little miffed because it took some time to figure out why our
executors suddenly started failing with jar-not-found errors :)
I'd prefer a full solution; last modified time runs into an issue if the
executor lies dormant for a week. You might say, "that's unlikely", but I'd
say, "it'll happen to someone, and they'll be a little miffed." The worker
should have enough state to figure out which executors are currently active,
though I'm not sure if the problem is made more difficult by multi-worker
scenarios.
---
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.
---
