Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/17297
@kayousterhout - Both the scenario A and B you described above are likely
(it totally depend on the nature of the job and available cluster resources)
and you are right that in case of scenario B, this PR will not provide any
benefit.
I am planning to have a follow up PR to make the fetch failure handling
logic better by not failing a task at all. In that case, the reducers can just
inform the scheduler of lost map output and can still continue processing other
available map outputs while the scheduler concurrently recomputes the lost map
output. But that will be a bigger change in the scheduler.
---
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
