You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Guangya Liu (JIRA)" <ji...@apache.org> on 2015/09/10 13:44:45 UTC
[jira] [Issue Comment Deleted] (MESOS-3184) Scheduler driver
accepts (re-)registration message while re-authentication is in progress.
[ https://issues.apache.org/jira/browse/MESOS-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guangya Liu updated MESOS-3184:
-------------------------------
Comment: was deleted
(was: A RR is here https://reviews.apache.org/r/38251/)
> 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
>
> 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)