Github user kxepal commented on the issue:
https://github.com/apache/spark/pull/15961
@srowen
> Why do you say it's so completely unactionable that nobody should know
about it?
That's just from my experience: in all the cases when drivers dies, it dies
in the middle of something, when you do some computations. In this case you
already get the Py4J exception on the next operation that triggers
communication with JVM process. You already knows about the problem and you're
going to fix anyway. So additional reminder on `sc.stop()` was looked redundant
for me.
> what's the downside to giving this information versus making it
impossible to tell that the JVM failed to shut down?
Perfect question! Well, I don't have any strong argument here. It seems
like a matter of taste about logging information usefulness.
Ok, I'll add a warning. Does the following looks good for you?:
```python
warning.warn(RuntimeWarning,
'Unable to stop JVM process. Probably, it was crashed or
externally killed')
```
---
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]
