Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47138072
i can simulate "Cannot connect to master" w/ pyspark --master
spark://localhost:12345 (where 12345 is a bogus port)
i see what you're seeing, no error and an apparent hang on actions.
however, it's not truly a hang, the action will error out with a visible
exception "Job aborted due to stage failure: All masters are unresponsive!
Giving up." i'll agree that's not ideal user experience, but it's different
from the functional hang that is described in SPARK-2244 and SPARK-2242.
imho - (a) is an urgent functional issue, (b) is not.
---
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.
---
