Hi Joseph
The error code is being reported as 0, and there is not much else in the
logs.
Regards
Sumit Chawla
On Wed, May 24, 2017 at 12:21 AM, Joseph Wu wrote:
> There isn't a tool for this. Can you check if the Mesos agent is being
> restarted (or crashing) when you
There isn't a tool for this. Can you check if the Mesos agent is being
restarted (or crashing) when you launch a task? And perhaps upload some
logs around the time of the task launch.
There is a mismatch between the exit codes you've reported though. When
you see that log line in the sandbox
Hi Joseph
I am using 0.27.0. Is there any diagnosis tool or command line that i can
run to ascertain that why its happening?
Regards
Sumit Chawla
On Fri, May 19, 2017 at 2:31 PM, Joseph Wu wrote:
> What version of Mesos are you using? (Just based on the word "slave"
What version of Mesos are you using? (Just based on the word "slave" in
that error message, I'm guessing 0.28 or older.)
The "Failed to synchronize" error is something that can occur while the
agent is launching the executor. During the launch, the agent will create
a pipe to the executor
Hi
I am facing a peculiar issue on one of the slave nodes of our cluster. I
have a spark cluster with 40+ nodes. On one of the nodes, all tasks fail
with exit code 0.
ExecutorLostFailure (executor e6745c67-32e8-41ad-b6eb-8fa4d2539da7-S76
exited caused by one of the running tasks) Reason:
5 matches
Mail list logo