mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Quarfot Nielsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-3485) Make hook execution order deterministic
Date Tue, 13 Oct 2015 00:17:05 GMT

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

Niklas Quarfot Nielsen updated MESOS-3485:
------------------------------------------
    Story Points: 3

> 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)

Mime
View raw message