You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/09/23 20:09:04 UTC

[jira] [Assigned] (MESOS-3485) Make hook execution order deterministic

     [ https://issues.apache.org/jira/browse/MESOS-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

haosdent reassigned MESOS-3485:
-------------------------------

    Assignee: haosdent

> Make hook execution order deterministic
> ---------------------------------------
>
>                 Key: MESOS-3485
>                 URL: https://issues.apache.org/jira/browse/MESOS-3485
>             Project: Mesos
>          Issue Type: Improvement
>          Components: modules
>            Reporter: Felix Abecassis
>            Assignee: haosdent
>
> 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<string, Hook*>}}. 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)