mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8160) Support idempotent framework registration
Date Tue, 07 Nov 2017 07:23:00 GMT

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

Yan Xu commented on MESOS-8160:
-------------------------------

/cc [~adam-mesos] this is relevant to the point you made on MESOS-1719 "in DC/OS we'd like
to be able to ensure unique framework names and not just frameworkIDs".

> Support idempotent framework registration
> -----------------------------------------
>
>                 Key: MESOS-8160
>                 URL: https://issues.apache.org/jira/browse/MESOS-8160
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Yan Xu
>
> Right now when a framework registers/subscribes, the master assigns a framework ID to
it and send it back so the framework can use it to tear itself down on Mesos when it's done.
However if the framework fails to receive it (e.g., it fails over before it receives the ID),
it doesn't have a way to do the teardown or failover.
> One apparent solution would be to allow the frameworks to supply the framework IDs themselves
but it may be easier for backwards compatibility to come up with a new framework supplied
"unique name/handle" concept to allow the framework to identify itself.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message