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

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

    [ https://issues.apache.org/jira/browse/MESOS-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997958#comment-15997958 ] 

Lei Xu edited comment on MESOS-2842 at 5/5/17 8:57 AM:
-------------------------------------------------------

We meet the same problem this week, and the logs show us "Check failed: metrics->frameworks.contains(principal.get())", I think this issue may be the root cause of our problem.

Our mesos version is 0.28.2


was (Author: brickxu):
We meet the same problem this week, and the logs show us "Check failed: metrics->frameworks.contains(principal.get())", I think this issue may be the root cause of our problem.

> 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
>            Priority: Critical
>              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.15#6346)