entActor: Executor updated:
> app-20140708100139-/6 is now RUNNING
> 14/07/08 10:01:45 INFO AppClient$ClientActor: Executor updated:
> app-20140708100139-/4 is now FAILED (Command exited with code 1)
> 14/07/08 10:01:45 INFO SparkDeploySchedulerBackend: Executor
> ap
+0530
Subject: Re: Spark: All masters are unresponsive!
From: ak...@sigmoidanalytics.com
To: user@spark.apache.org
Are you sure this is your master URL spark://pzxnvm2018:7077 ?
You can look it up in the WebUI (mostly http://pzxnvm2018:8080) top left
corner. Also make sure you are able to telnet pzxn
Are you sure this is your master URL spark://pzxnvm2018:7077 ?
You can look it up in the WebUI (mostly http://pzxnvm2018:8080) top left
corner. Also make sure you are able to telnet pzxnvm2018 7077 from the
machines where you are running the spark shell.
Thanks
Best Regards
On Tue, Jul 8, 2014
Hi All,
I am having a few issues with stability and scheduling. When I use spark shell
to submit my application. I get the following error message and spark shell
crashes. I have a small 4-node cluster for PoC. I tried both manual and
scripts-based cluster set up. I tried using FQDN as well for
