You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2015/07/17 19:19:05 UTC

[jira] [Assigned] (MESOS-3068) Registry operations are hardcoded for a single key (Registry object)

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

Joseph Wu reassigned MESOS-3068:
--------------------------------

    Assignee: Joseph Wu

> Registry operations are hardcoded for a single key (Registry object)
> --------------------------------------------------------------------
>
>                 Key: MESOS-3068
>                 URL: https://issues.apache.org/jira/browse/MESOS-3068
>             Project: Mesos
>          Issue Type: Task
>          Components: master, replicated log
>            Reporter: Joseph Wu
>            Assignee: Joseph Wu
>              Labels: mesosphere
>
> This is primarily a refactoring.
> The prototype for modifying the registry is currently:
> {code}
> Try<bool> operator () (
>     Registry* registry,
>     hashset<SlaveID>* slaveIDs,
>     bool strict);
> {code}
> In order to support Maintenance schedules (possibly Quotas as well), there should be an alternate prototype for Maintenance.  Something like:
> {code}
> Try<bool> operation () (
>     Maintenance* maintenance,
>     bool strict);
> {code}
> The existing RegistrarProcess::update (src/master/registrar.cpp) should be refactored to allow for more than one key.  If necessary, refactor existing operations defined in src/master/master.hpp (AdminSlave, ReadminSlave,  RemoveSlave).



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