You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Zhitao Li (JIRA)" <ji...@apache.org> on 2016/09/08 21:37:20 UTC

[jira] [Commented] (MESOS-6101) Add event for Framwork added to master operator API

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

Zhitao Li commented on MESOS-6101:
----------------------------------

[~vinodkone] [~anandmazumdar], for completeness, I think we have two events:

1. FRAMEWORK_ADDED, which maps to the case when a FRAMEWORK_INFO is first known to the master;
2. FRAMEWORK_REMOVED, which maps to the case when a FRAMEWORK_INFO.

It's open to me whether we need event for framework failover/disconnect/reconnect, but I guess it's probably fine to leave for next iteration?

https://reviews.apache.org/r/51700/ has patch for FRAMEWORK_ADDED, I'll start one for FRAMEWORK_REMOVED.

> Add event for Framwork added to master operator API
> ---------------------------------------------------
>
>                 Key: MESOS-6101
>                 URL: https://issues.apache.org/jira/browse/MESOS-6101
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Zhitao Li
>            Assignee: Zhitao Li
>
> Consider the following case:
> 1) a subscriber connects to master;
> 2) a new scheduler registered as a new framework;
> 3) a task is launched from this framework.
> In this sequence, subscriber does not have a way to know the FrameworkInfo belonging to the FrameworkId.
> We should support an event (e.g. when framework info in master is added/changed).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)