You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Ilya Pronin (JIRA)" <ji...@apache.org> on 2017/03/22 11:36:41 UTC

[jira] [Commented] (MESOS-7281) Backwards incompatible UpdateFrameworkMessage handling

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

Ilya Pronin commented on MESOS-7281:
------------------------------------

Review request: https://reviews.apache.org/r/57836/

[~mcypark] since you wrote the original patch, can you shepherd this please?

> Backwards incompatible UpdateFrameworkMessage handling
> ------------------------------------------------------
>
>                 Key: MESOS-7281
>                 URL: https://issues.apache.org/jira/browse/MESOS-7281
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>            Reporter: Ilya Pronin
>            Assignee: Ilya Pronin
>
> Patch in [r/57108|https://reviews.apache.org/r/57108/] introduced framework info updates. Agents are using a new {{framework_info}} field without checking that it's present. If a patched agent is used with not patched master it will get a default-initialized {{framework_info}}. This will cause agent failures later. E.g abort on framework ID validation when it tries to launch a new task for the updated framework.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)