I have a question on the Executors. I see that a framework can use 1 or
more executors on a slave. At finest granularity, one could launch each
task in a separate executor (our tasks are relatively long lived). This at
least seems like a good choice since resource isolation of executors now
happens for each task. And, I could eliminate the work in my executor of
forking processes to execute tasks.

When a task completes (either normally or by getting a kill request), I
would like the executor to exit as well. Playing with this, I have the
status of TASK_COMPLETED being sent via the driver, followed by a wait of
about 5 secs (not sure I need this for any mesos communication to happen
for status), and then, say, a System.exit(). However, this is producing a
TASK_LOST to my framework scheduler. Shouldn't the previous sending of
TASK_COMPLETED status prevent the TASK_LOST update?

I am using Mesos 0.16.

Sharma

Reply via email to