Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/17088
Even if I completely agreed that removing all of the shuffle files on a
host was the correct design choice, I'd still be hesitant to merge this right
now. That is simply because we have recently merged other changes related to
fetch failure handling, and I'd really like to see some more time pass with
just those changes in the code before we introduce more fetch failure changes.
I don't want to get in the situation of merging this PR then getting reports of
fetch failure bugs in master a week later, and not knowing whether to place the
blame on this PR or the other recent fetch failure changes.
That needn't preclude more discussion of this PR or possibly merging it
after we have a little more experience and confidence with the code already in
master.
/cc @kayousterhout @squito
---
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
