Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15037
It looks like this location refresh logic was added in #11241 in order to
resolve some issues which could occur on dynamic allocation clusters with high
churn. While I definitely think that we should either fix the bug in this retry
logic (or, better yet, move this logic higher up so that it's easier to
understand and more obviously correct), I propose to do this in a separate
patch so that this smaller fix can be backported independently into Spark
1.6.x. Let me go ahead and file a followup JIRA now.
---
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]
