Project: mesos
Issue MESOS-3485: Make hook execution order deterministic
Currently, when using multiple hooks of the same type, the execution order is implementation-defined. This is because in src/hook/manager.cpp, the list of available hooks is stored in a {{hashmap}}. A hashmap is probably unnecessary for this task since the number of hooks should remain reasonable. A data structure preserving ordering should be used instead to allow the user to predict the execution order of the hooks. I suggest that the execution order should be the order in which hooks are specified with {{--hooks}} when starting an agent/master. This will be useful when combining multiple hooks after MESOS-3366 is done.
Story points: 3