[jira] [Commented] (MESOS-881) Tests are slow because the scheduler attempts to authenticate before the master realizes it is elected.

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

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

Yan Xu commented on MESOS-881:
------------------------------

https://reviews.apache.org/r/16742/

> Tests are slow because the scheduler attempts to authenticate before the master realizes it is elected.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-881
>                 URL: https://issues.apache.org/jira/browse/MESOS-881
>             Project: Mesos
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.16.0
>            Reporter: Benjamin Mahler
>            Assignee: Yan Xu
>             Fix For: 0.17.0
>
>
> Many of the tests are often slow O(5 seconds) due to the race between the scheduler detecting the leader and the master detecting that it is the leader.
> When the scheduler wins and the master drops the authentication request (because it's not yet leading), the scheduler retries after 5 seconds.
> A few possible solutions here:
> 1. Have each test wait for Master::detected (this will bloat a lot of the tests).
> 2. Have StartMaster() wait for Master::detected, this is cleaner.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)