Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15037
Although the location refresh will reset `runningFailureCount`, the loop
here should still terminate because it's based off of `totalFailureCount`,
which is monotonically increasing. I agree that this is a bit confusing,
though: it might make sense to automatically skip any locations which have been
tried previously (even before the refresh), since the master might continue to
report invalid locations.
---
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
