[jira] [Issue Comment Deleted] (MESOS-2217) Modules loading should be transactional

["Gavin (JIRA)" <ji...@apache.org>]

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

Gavin updated MESOS-2217:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Modules loading should be transactional
> ---------------------------------------
>
>                 Key: MESOS-2217
>                 URL: https://issues.apache.org/jira/browse/MESOS-2217
>             Project: Mesos
>          Issue Type: Bug
>          Components: modules
>            Reporter: Alexander Rukletsov
>            Priority: Minor
>              Labels: integration, mesosphere
>
> If multiple modules are provided to Mesos, say A, B, C, the module manager tries to load them one by one until all are successfully loaded or a load error occurs. If loading fails at a particular library, the manager neither unloads all of the already loaded libraries, nor tries to load the rest of provided modules. For example, if modules A, B, and C are loaded (in that sequence), and B fails to load, A stays loaded and C not; however, if we change the sequence to C, B, A and B fails again, then we'll have C loaded and A not.
> We would like to have a sort of transactional behaviour here: either we load all or none, or we load modules one by one and load failure in one doesn't influence others. Right now, we do have "all or none" behaviour, because Mesos process exits in case of any error during modules loading. This may obviously change with hooks / decorators landed, therefore we should add proper transaction here for consistency and error resilience.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)