https://github.com/apache/aurora/blob/aae2b0dc73b7534c66982ed07b1f029150e245de/src/main/java/org/apache/aurora/scheduler/mesos/SchedulerDriverModule.java
https://github.com/apache/aurora/blob/aae2b0dc73b7534c66982ed07b1f029150e245de/src/main/java/org/apache/aurora/scheduler/mesos/VersionedSchedulerDriverService.java#L50 On Tue, Jan 9, 2018 at 1:21 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote: > David, > Where can I find this code? > > Mohit. > > On Sat, Dec 9, 2017 at 4:27 PM, David McLaughlin <dmclaugh...@apache.org> > wrote: > >> The new API is present in Aurora in a compatibility layer, but the HTTP >> performance issues still exist so we can't make it the default. >> >> On Sat, Dec 9, 2017 at 4:24 PM, Bill Farner <wfar...@apache.org> wrote: >> >>> Aurora pre-dates SHUTDOWN by several years, so the option was not >>> present. Additionally, the SHUTDOWN call is not available in the API used >>> by Aurora. Last i knew, Aurora could not use the "new" API because of >>> performance issues in the implementation, but i do not know where that >>> stands today. >>> >>> https://mesos.apache.org/documentation/latest/scheduler-http >>> -api/#shutdown >>> >>>> NOTE: This is a new call that was not present in the old API >>> >>> >>> On Sat, Dec 9, 2017 at 4:11 PM, Mohit Jaggi <mohit.ja...@uber.com> >>> wrote: >>> >>>> Folks, >>>> Our Mesos team is wondering why Aurora chose KILL over SHUTDOWN for >>>> killing tasks. As Aurora has an executor per task, won't SHUTDOWN work >>>> better? It will avoid zombie executors. >>>> >>>> Mohit. >>>> >>> >>> >> >
