You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Charles Reiss (Updated) (JIRA)" <ji...@apache.org> on 2012/03/20 08:45:45 UTC

[jira] [Updated] (MESOS-168) Really bad timing can cause one framework PID to be registered with two IDs

     [ https://issues.apache.org/jira/browse/MESOS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Reiss updated MESOS-168:
--------------------------------

    Description: 
If message delivery is delayed enough, it's possible for a framework not to receive its FrameworkRegisteredMessage (with ID "A") before its (one second) timer to resend its RegisterFrameworkMessage (as part of reliable registration). The master will happily register the same framework PID again with a different framework ID (with ID "B"). The framework will receive offers for both ID "A" and ID "B", but will reply to offers as ID "B", causing the framework to CHECK()-fail when it checks the validity of the offers.


  was:
If message delivery is delayed enough, it's possible for a framework not to receive its FrameworkRegisteredMessage (with ID "A") before its (one second) timer to resend its RegisterFrameworkMessage (as part of reliable registration). The master will happily register the same framework PID again with a different framework ID (with ID "B"). The framework will receive offers for both ID "A" and ID "B", but will reply to offers as ID "B", causing the master to CHECK()-fail when it checks the validity of the offer replies.


    
> Really bad timing can cause one framework PID to be registered with two IDs
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-168
>                 URL: https://issues.apache.org/jira/browse/MESOS-168
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Charles Reiss
>
> If message delivery is delayed enough, it's possible for a framework not to receive its FrameworkRegisteredMessage (with ID "A") before its (one second) timer to resend its RegisterFrameworkMessage (as part of reliable registration). The master will happily register the same framework PID again with a different framework ID (with ID "B"). The framework will receive offers for both ID "A" and ID "B", but will reply to offers as ID "B", causing the framework to CHECK()-fail when it checks the validity of the offers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira