unsubscribe

Sent from Mail for Windows 10

Re: orphan executor

:-) Is there a Jira ticket to track this? Any idea when this will be worked on? On Tue, Oct 31, 2017 at 5:22 PM, Benjamin Mahler wrote: > The question was posed merely to point out that there is no notion of the > executor "running away" currently, due to the answer I

Re: orphan executor

The question was posed merely to point out that there is no notion of the executor "running away" currently, due to the answer I provided: there isn't a complete lifecycle API for the executor. (This includes healthiness, state updates, reconciliation, ability for scheduler to shut it down, etc).

Re: orphan executor

Good question. - I don't know what the interaction between mesos agent and executor is. Is there a health check? - There is a reconciliation between Mesos and Frameworks: will Mesos include the "orphan" executor in the list there, so framework can find runaways and kill them(using Mesos provided

Re: orphan executor

What defines a runaway executor? Mesos does not know that this particular executor should self-terminate within some reasonable time after its task terminates. In this case the framework (Aurora) knows this expected behavior of Thermos and can clean up ones that get stuck after the task

Re: orphan executor

I was asking if this can happen automatically. On Tue, Oct 31, 2017 at 2:41 PM, Benjamin Mahler wrote: > You can kill it manually by SIGKILLing the executor process. > Using the agent API, you can launch a nested container session and kill > the executor. +jie,gilbert, is

Re: orphan executor

You can kill it manually by SIGKILLing the executor process. Using the agent API, you can launch a nested container session and kill the executor. +jie,gilbert, is there a CLI command for 'exec'ing into the container? On Tue, Oct 31, 2017 at 12:47 PM, Mohit Jaggi wrote: >

Re: orphan executor

Yes. There is a fix available now in Aurora/Thermos to try and exit in such scenarios. But I am curious to know if Mesos agent has the functionality to reap runaway executors. On Tue, Oct 31, 2017 at 12:08 PM, Benjamin Mahler wrote: > Is my understanding correct that the

Re: Subscribe to an active framework through HTTP API Scheduler

Someone worked on it (new operator api call) during the Mesoscon EU hackathon. They were planning to send a review once they wrap it up. On Tue, Oct 31, 2017 at 12:11 PM, Benjamin Mahler wrote: > There had been discussion to support killing tasks from the operator API, > but

Re: Finding Tasks Waiting for Resources in Mesos

I think you need to query the framework that you are running on top of Mesos for this information. The workflow is as follows: User submits a task to framework, framework waits for resources to be available in Mesos cluster, once available it launches the task. On Tue, Oct 31, 2017 at 11:16 AM,

Re: Finding Tasks Waiting for Resources in Mesos

+ User Group. --Senthil On Tue, Oct 31, 2017 at 11:44 PM, SenthilKumar K wrote: > Hi All , What is the way to Query Mesos Cluster to Check whether the task > is waiting for Resources or not? > > Context : > Say 10 tasks are running and Mesos Cluster Usage is :