You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:22 UTC
[jira] [Issue Comment Deleted] (MESOS-2380) Mesos Anonymous Modules
[ https://issues.apache.org/jira/browse/MESOS-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated MESOS-2380:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> Mesos Anonymous Modules
> -----------------------
>
> Key: MESOS-2380
> URL: https://issues.apache.org/jira/browse/MESOS-2380
> Project: Mesos
> Issue Type: Improvement
> Components: agent, master, modules
> Reporter: Till Toenshoff
> Assignee: Till Toenshoff
> Priority: Major
>
> A new kind of module that does *not* receive any callbacks but simply coexists with its parent process.
> h4.Motivation and Use Cases
> We want to add customized and experimental capabilities that concern the life time of Mesos components without protruding into Mesos source code and without creating new build process dependencies for everybody.
> Example use cases:
> 1. An anonymous module that gathers fail-over incidents and reports summaries thereof to a remote data sink.
> 2. A slave module that observes host computer metrics and correlates these with task activity. This can be used to find resources leaks and to prevent, respectively guide, oversubscription.
> 3. Upgrades and provisioning that require shutdown and restart.
> h4.Module Classification
> Unlike other named modules, an anonymous module does not directly replace or provide essential Mesos functionality (such as an Isolator module does). Unlike a decorator module it does not directly add or inject data into Mesos core either.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)