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

Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/09/17 20:00:35 UTC

[jira] [Comment Edited] (MESOS-1784) Design the semantics for updating FrameworkInfo

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

Vinod Kone edited comment on MESOS-1784 at 9/17/14 6:00 PM:
------------------------------------------------------------

https://cwiki.apache.org/confluence/display/MESOS/Design+doc:+Updating+Framework+Info


was (Author: vinodkone):
https://docs.google.com/document/d/1vEBuFN9mm3HkrNCmkAuwX-4kNYv0MwjUecLE3Jp_BqE/edit?usp=sharing

> Design the semantics for updating FrameworkInfo
> -----------------------------------------------
>
>                 Key: MESOS-1784
>                 URL: https://issues.apache.org/jira/browse/MESOS-1784
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>
> Currently, there is no easy way for frameworks to update their FrameworkInfo., resulting in issues like MESOS-703 and MESOS-1218.
> This ticket captures the design for doing FrameworkInfo update without having to roll masters/slaves/tasks/executors.



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