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

["Andy Cook (JIRA)" <ji...@apache.org>]

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

Andy Cook commented on MESOS-7619:
----------------------------------

Hello,

Please find the {{state.json}} info attached.  I've removed all of the info about running and completed tasks.  The old framework (with all of the running tasks) is {{80f08ece-91c7-43cb-bae7-6a2b41e25ec0-0001}}.  You'll see in the screenshot that Mesos believes it was registered 47 years ago.  Similarly, the state.json shows a registered_time of {{0}}.

{noformat}
      "failover_timeout":604800.0,
      "checkpoint":true,
      "registered_time":0.0,
      "unregistered_time":0.0,
{noformat}

> 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, state.json
>
>
> 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)