Github user ilganeli commented on the pull request:
https://github.com/apache/spark/pull/5636#issuecomment-95339230
@squito Given that we can't check against the failure message, any ideas on
what we can do instead? Is this information exposed in any way at the level of
the ```DAGScheduler``` or do I need to figure out a mechanism to propagate the
error info up in a more detailed way. I can add the config change to allow
infinite retries and I'll add the clear at the end of the job - that seems
reasonable.
---
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]
