I'm working on porting my executor from the CommandExecutor to a custom executor, in order to take advantage of other features of Mesos. I started by changing the TaskInfo in the scheduler to define ExecutorInfo instead of CommandInfo, where the ExecutorInfo's command is the same as the original CommandInfo. I gave the executor a random ID.
I can see that the executor successfully starts and seems to connect to Mesos. After a few moments (10s - 100s of ms), the executor fails with the LOST status. Am I responsible for explicitly managing the TaskState lifecycle of the executor? That is, do I need to immediately send the TASK_STARTING status update, and then send the TASK_RUNNING update once the task has begun? Are there any heartbeats that I'm responsible for? Thanks, David
