You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2016/07/31 07:57:20 UTC

[jira] [Updated] (MESOS-2842) Update FrameworkInfo.principal on framework re-registration

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

Adam B updated MESOS-2842:
--------------------------
    Assignee:     (was: Aditi Dixit)

> Update FrameworkInfo.principal on framework re-registration
> -----------------------------------------------------------
>
>                 Key: MESOS-2842
>                 URL: https://issues.apache.org/jira/browse/MESOS-2842
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>              Labels: security
>
> From the design doc:
> This is a bit involved because ‘principal’ is used for authentication and rate limiting.
> The authentication part is straightforward because a framework with updated ‘principal’ should authenticate with the new ‘principal’ before being allowed to re-register. The ‘authenticated’ map already gets updated when the framework disconnects and reconnects, so it is fine.
> For rate limiting, Master:failoverFramework() needs to be changed to update the principal in ‘frameworks.principals’ map and also remove the metrics for the old principal if there are no other frameworks with this principal (similar to what we do in Master::removeFramework()).
> The Master::visit() and Master::_visit() should work with the current semantics.



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