Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15737
I don't think these cases are comparable, silently swallowing offset out of
range is dropping data on the floor. In contrast, networks _are_ transiently
flakey and we should be robust to that here like we are in all of the other
parts of Spark. Specifically, we should probably use `spark.network.timeout`
if they haven't overridden this particular setting (which defaults to 120s).
---
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]
