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

Posted to issues@mesos.apache.org by "Ken Sipe (JIRA)" <ji...@apache.org> on 2017/06/05 16:59:04 UTC

[jira] [Updated] (MESOS-7619) Framework Upgrade Resulting in Jan 1, 1070 Date

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

Ken Sipe updated MESOS-7619:
----------------------------
    Attachment: Pasted image at 2017_05_31 09_30 AM.png

screen shot

> Framework Upgrade Resulting in Jan 1, 1070 Date
> -----------------------------------------------
>
>                 Key: MESOS-7619
>                 URL: https://issues.apache.org/jira/browse/MESOS-7619
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Ken Sipe
>         Attachments: Pasted image at 2017_05_31 09_30 AM.png
>
>
> In the process of upgrading Apache Mesos and Marathon (in HA mode).. marathon ended up with a new framework ID and the older framework ID is listed as being from Jan 1, 1970 (47 years ago).
> The issue with Marathon getting a new framework Id is understood and was worked out with mesosphere's marathon team.  Must of the detail is in the #marathon channel of Apache Mesos slack.



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