There should be a WARNING log line in the mesos slave log (typically /var/log/mesos/mesos-slave.INFO) that says "Shutting down executor ... because ..." probably right after the line that says "Got registration for executor ..." Can you post a gist of the relevant slave log lines?
On Thu, Jan 8, 2015 at 11:39 AM, Srinivas Murthy <[email protected]> wrote: > Its a custom executor, I can see each of the nodes have > /tmp/mesos/...executors/..runs/../latest with stderr and stdout, along with > the jar file. > My stdout, is blank, while the stderr has "Executor asked to shutdown" as > its last line, after the URI is accessed and the resource jar is fetched.. > > > On Thu, Jan 8, 2015 at 11:29 AM, Adam Bordelon <[email protected]> wrote: > >> Is your "adhoc framework" using the default Mesos executor, or does it >> use a custom executor? >> You can check the task/executor's sandbox from the Mesos web UI, to see >> if the custom executor or other URIs were properly downloaded, and to view >> the stdout/stderr of the executor/task. >> >> On Thu, Jan 8, 2015 at 10:14 AM, Srinivas Murthy <[email protected]> >> wrote: >> >>> I am running a cluster with one master node and three slaves. >>> Just got hold of a tutorial code from Git that runs an adhoc framework >>> written in Java, nothing fancy. >>> All I am getting is " Executor asked to shutdown" and the code exits >>> gracefully, no exceptions. I am trying to put some logging statements in >>> all the callback functions, but looks like the Executors are invoked but >>> never run. >>> Any clues on how to debug this? >>> I am running Mesos 0.21 and JDK 1.7.55. >>> >>> Regards >>> Srinivas >>> >> >> >
