Mailing-List: contact user-help@spark.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@spark.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of scrapcodes@gmail.com designates
 74.125.82.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACwKa9e-OZvw+LEO0K+cZ14KbwJMqpk0W5hQ62KbZyNBLOXEHQ@mail.gmail.com>
References: 
 <CACwKa9e-OZvw+LEO0K+cZ14KbwJMqpk0W5hQ62KbZyNBLOXEHQ@mail.gmail.com>
From: Prashant Sharma <scrapcodes@gmail.com>
Date: Thu, 21 Nov 2013 19:18:20 +0530
Message-ID: 
 <CAOYDGoB6tFeebsyS+VGbP9vD42ZjEMabjtFhZcDT=Yaa6UdJUw@mail.gmail.com>
Subject: Re: problems with launching executor in standalone cluster
To: user@spark.incubator.apache.org
Content-Type: multipart/alternative; boundary=089e01161d3ebf504b04ebb02700

--089e01161d3ebf504b04ebb02700
Content-Type: text/plain; charset=ISO-8859-1

You might wanna check the stderr and stdout located in work(where
standalone puts log of Executors ) directory.


On Thu, Nov 21, 2013 at 7:07 PM, Umar Javed <umarj.javed@gmail.com> wrote:

> I have a really simple standalone cluster with one worker located on the
> same machine as the master. Both master and worker launch OK with the
> scripts provided in /conf. However when I run the spark shell with the
> command: MASTER=.... ./spark-shell, my worker fails to launch. Here's a
> section of the log output:
>
> 13/11/21 06:32:34 INFO SparkDeploySchedulerBackend: Executor
> app-20131121063231-0000/4 removed: Command exited with code 1
> 13/11/21 06:32:34 INFO Client$ClientActor: Executor added:
> app-20131121063231-0000/5 on worker-20131121063035-node0-link0-52768
> (node0-link0:7077) with 2 cores
> 13/11/21 06:32:34 INFO SparkDeploySchedulerBackend: Granted executor ID
> app-20131121063231-0000/5 on hostPort node0-link0:7077 with 2 cores, 512.0
> MB RAM
> 13/11/21 06:32:34 INFO Client$ClientActor: Executor updated:
> app-20131121063231-0000/5 is now RUNNING
> 13/11/21 06:32:34 INFO Client$ClientActor: Executor updated:
> app-20131121063231-0000/5 is now FAILED (Command exited with code 1)
> 13/11/21 06:32:34 INFO SparkDeploySchedulerBackend: Executor
> app-20131121063231-0000/5 removed: Command exited with code 1
>
>
> Basically the executor on the worker keeps getting failed as soon as it is
> launched.
> Anybody have a solution?
>
> thanks!
> Umar
>


-- 
s

--089e01161d3ebf504b04ebb02700
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You might wanna check the stderr and stdout located in wor=
k(where standalone puts log of Executors ) directory.=A0</div><div class=3D=
"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Nov 21, 2013 at 7:=
07 PM, Umar Javed <span dir=3D"ltr">&lt;<a href=3D"mailto:umarj.javed@gmail=
.com" target=3D"_blank">umarj.javed@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I have a really simple stan=
dalone cluster with one worker located on the same machine as the master. B=
oth master and worker launch OK with the scripts provided in /conf. However=
 when I run the spark shell with the command: MASTER=3D.... ./spark-shell, =
my worker fails to launch. Here&#39;s a section of the log output:<div>


<br></div><div><div>13/11/21 06:32:34 INFO SparkDeploySchedulerBackend: Exe=
cutor app-20131121063231-0000/4 removed: Command exited with code 1</div><d=
iv>13/11/21 06:32:34 INFO Client$ClientActor: Executor added: app-201311210=
63231-0000/5 on worker-20131121063035-node0-link0-52768 (node0-link0:7077) =
with 2 cores</div>


<div>13/11/21 06:32:34 INFO SparkDeploySchedulerBackend: Granted executor I=
D app-20131121063231-0000/5 on hostPort node0-link0:7077 with 2 cores, 512.=
0 MB RAM</div><div>13/11/21 06:32:34 INFO Client$ClientActor: Executor upda=
ted: app-20131121063231-0000/5 is now RUNNING</div>


<div>13/11/21 06:32:34 INFO Client$ClientActor: Executor updated: app-20131=
121063231-0000/5 is now FAILED (Command exited with code 1)</div><div>13/11=
/21 06:32:34 INFO SparkDeploySchedulerBackend: Executor app-20131121063231-=
0000/5 removed: Command exited with code 1</div>


</div><div><br></div><div><br></div><div>Basically the executor on the work=
er keeps getting failed as soon as it is launched.</div><div>Anybody have a=
 solution?</div><div><br></div><div>thanks!</div><span class=3D"HOEnZb"><fo=
nt color=3D"#888888"><div>

Umar</div></font></span></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>s
</div>

--089e01161d3ebf504b04ebb02700--