You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kapil Arya (JIRA)" <ji...@apache.org> on 2016/03/11 07:56:40 UTC
[jira] [Updated] (MESOS-4916) Allow modules to express if they are
multi-instantiable and thread safe.
[ https://issues.apache.org/jira/browse/MESOS-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kapil Arya updated MESOS-4916:
------------------------------
Story Points: 8
> Allow modules to express if they are multi-instantiable and thread safe.
> ------------------------------------------------------------------------
>
> Key: MESOS-4916
> URL: https://issues.apache.org/jira/browse/MESOS-4916
> Project: Mesos
> Issue Type: Task
> Reporter: Kapil Arya
> Labels: mesosphere
>
> A module might be instantiated multiple time (e.g., multiple schedulers in the same Java process instantiating an authenticator module) within the same process. The current mechanism doesn't provide a way through the module API to forbid multiple instantiations. It is up to the module to check and return error on prior instantiation.
> Along similar lines, a module should be able to express thread-safety concerns. Typically, a module running in Master/Agent doesn't have to be concerned about thread safety if it uses libprocess API. However, we should investigate how it plays in the scheduler environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)