[jira] [Commented] (MESOS-786) Update semantics of when framework registered()/reregistered() get called

["Bill Farner (JIRA)" <ji...@apache.org>]

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

Bill Farner commented on MESOS-786:
-----------------------------------

Are there use cases you're thinking of that push for (2) and (3) to be different from the framework's perspective?  The 'state machine' i had in mind was something like:

I assumed this was the call flow:
{noformat}
 Following+-->Registered+--->Disconnected+-------+
                                   ^             |
                                   |             |
                                   +             |
                             Re-registered<------+
{noformat}

In this flow, a framework can use registered as a one-time startup signal, and re-registered/disconnected are advisory.







> Update semantics of when framework registered()/reregistered() get called
> -------------------------------------------------------------------------
>
>                 Key: MESOS-786
>                 URL: https://issues.apache.org/jira/browse/MESOS-786
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>             Fix For: 0.16.0
>
>
> Current semantics:
> 1) Framework connects w/ master very first time --> registered()
> 2) Framework reconnects w/ same master after a zk blip --> reregistered()
> 3) Framework reconnects w/ failed over master --> registered()
> 4) Failed over framework connects w/ same master --> registered()
> 5) Failed over framework connects w/ failed over master --> registered() 
> Updated semantics:
> Everything same except 
> 3) Framework reconnects w/ failed over master --> reregistered()



--
This message was sent by Atlassian JIRA
(v6.1#6144)