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 <[email protected]> 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 <[email protected]> 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. >> > >
