You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2015/05/01 17:24:12 UTC

[jira] [Updated] (MESOS-2317) Remove deprecated checkpoint=false code

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

Bernd Mathiske updated MESOS-2317:
----------------------------------
    Sprint: Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15  (was: Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1)

> Remove deprecated checkpoint=false code
> ---------------------------------------
>
>                 Key: MESOS-2317
>                 URL: https://issues.apache.org/jira/browse/MESOS-2317
>             Project: Mesos
>          Issue Type: Epic
>    Affects Versions: 0.22.0
>            Reporter: Adam B
>            Assignee: Joerg Schad
>              Labels: checkpoint, mesosphere
>
> Cody's plan from MESOS-444 was:
> 1) -Make it so the flag can't be changed at the command line-
> 2) -Remove the checkpoint variable entirely from slave/flags.hpp. This is a fairly involved change since a number of unit tests depend on manually setting the flag, as well as the default being non-checkpointing.-
> 3) Remove logic around checkpointing in the slave
> 4) Drop the flag from the SlaveInfo struct, remove logic inside the master (Will require a deprecation cycle).



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