[jira] [Commented] (MESOS-3184) Scheduler driver accepts (re-)registration message while re-authentication is in progress.

["Barry Kaplan (JIRA)" <ji...@apache.org>]

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

Barry Kaplan commented on MESOS-3184:
-------------------------------------

I think I'm seeing with with kafka-mesos. It was working great for some time, but all of the sudden I get:

I1114 07:39:52.281263 16742 master.cpp:2084] Refusing subscription of framework 'kafka' at scheduler-a32d6aa0-a6b0-4ce3-a0af-0f608545423a@127.0.0.1:41726: Framework has been removed

So far I can't get the scheduler to register anymore.

> Scheduler driver accepts (re-)registration message while re-authentication is in progress.
> ------------------------------------------------------------------------------------------
>
>                 Key: MESOS-3184
>                 URL: https://issues.apache.org/jira/browse/MESOS-3184
>             Project: Mesos
>          Issue Type: Bug
>          Components: scheduler driver
>            Reporter: Benjamin Mahler
>            Assignee: Guangya Liu
>              Labels: security
>
> The scheduler driver currently accepts re-registered when it is re-authenticating with the master. This can occur due a race with the authentication timeout and the master sending a (re-)registration message.
> This is fairly innocuous currently, but if the subsequent re-authentication fails, the driver keeps retrying authentication, but both the master and driver continue to act as though the scheduler is registered.
> The authentication check in _(re-)registerFramework in the master doesn't provide any benefit to this, it is still a race, so this should likely be removed as well.



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