''' SHUTDOWN <http://mesos.apache.org/documentation/latest/scheduler-http-api/#shutdown>
Sent by the scheduler to shutdown a specific custom executor (NOTE: This is a new call that was not present in the old API). When an executor gets a shutdown event, it is expected to kill all its tasks (and send TASK_KILLED updates) and terminate. If an executor doesn’t terminate within a certain timeout (configurable via the --executor_shutdown_grace_period agent flag), the agent will forcefully destroy the container (executor and its tasks) and transition its active tasks to TASK_LOST. ''' The forceful shutdown documented above makes it more robust than KILL. In Apache Aurora, an executor always runs only 1 task. On Wed, Jan 17, 2018 at 2:06 PM, Benjamin Mahler <[email protected]> wrote: > Can you tell us more about what the use case is? Why do you think it's > more robust? > > On Tue, Jan 16, 2018 at 8:41 PM Mohit Jaggi <[email protected]> wrote: > >> I am trying to change Apache Aurora's code to call SHUTDOWN instead of >> KILL. SHUTDOWN seems to offer more robust termination than KILL. >> >> On Tue, Jan 16, 2018 at 6:40 PM, Benjamin Mahler <[email protected]> >> wrote: >> >>> Mohit, what are you trying to accomplish by going from KILL to SHUTDOWN? >>> >>> On Tue, Jan 16, 2018 at 5:15 PM, Joseph Wu <[email protected]> wrote: >>> >>>> If a framework launches tasks, then it will use an executor. Mesos >>>> provides a "default" executor if the framework doesn't explicitly specify >>>> an executor. (And the Shutdown call will work with that default executor.) >>>> >>>> On Tue, Jan 16, 2018 at 4:49 PM, Mohit Jaggi <[email protected]> >>>> wrote: >>>> >>>>> Gotcha. Another question: if a framework doesn't use executors, can it >>>>> still use the SHUTDOWN call? >>>>> >>>>> On Fri, Jan 12, 2018 at 2:37 PM, Anand Mazumdar < >>>>> [email protected]> wrote: >>>>> >>>>>> Yes; It's a newer interface that still allows you to switch between >>>>>> the v1 (new) and the old API. >>>>>> >>>>>> -anand >>>>>> >>>>>> On Fri, Jan 12, 2018 at 3:28 PM, Mohit Jaggi <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Are you suggesting >>>>>>> >>>>>>> *send(new Call(METHOD, Param1, ...)) * >>>>>>> >>>>>>> instead of >>>>>>> >>>>>>> *driver.method(Param1, ....)* >>>>>>> >>>>>>> *?* >>>>>>> >>>>>>> On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Mohit, >>>>>>>> >>>>>>>> You can use the V1Mesos class that uses the v1 API internally >>>>>>>> allowing you to send the 'SHUTDOWN' call. We also have a V0Mesos class >>>>>>>> that >>>>>>>> uses the old scheduler driver internally. >>>>>>>> >>>>>>>> -anand >>>>>>>> >>>>>>>> On Wed, Jan 10, 2018 at 2:53 PM, Mohit Jaggi <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks Vinod. Is there a V1SchedulerDriver.java file? I see >>>>>>>>> https://github.com/apache/mesos/tree/ >>>>>>>>> 72752fc6deb8ebcbfbd5448dc599ef3774339d31/src/java/src/org/ >>>>>>>>> apache/mesos/v1/scheduler but it does not have a V1 driver. >>>>>>>>> >>>>>>>>> On Fri, Jan 5, 2018 at 3:59 PM, Vinod Kone <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> That's right. It is only available for v1 schedulers. >>>>>>>>>> >>>>>>>>>> On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi <[email protected] >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> Folks, >>>>>>>>>>> I am trying to change Apache Aurora's code to call SHUTDOWN >>>>>>>>>>> instead of KILL. However, it seems that the SchedulerDriver class >>>>>>>>>>> in Mesos >>>>>>>>>>> does not have a shutdownExecutor() call. >>>>>>>>>>> >>>>>>>>>>> https://github.com/apache/mesos/blob/ >>>>>>>>>>> 72752fc6deb8ebcbfbd5448dc599ef3774339d31/src/java/src/org/ >>>>>>>>>>> apache/mesos/SchedulerDriver.java >>>>>>>>>>> >>>>>>>>>>> Mohit. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Anand Mazumdar >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Anand Mazumdar >>>>>> >>>>> >>>>> >>>> >>> >>
