[
https://issues.apache.org/jira/browse/MESOS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157092#comment-14157092
]
Cody Maloney commented on MESOS-444:
------------------------------------
First patch to work on this: https://reviews.apache.org/r/26275
Email to mesos-dev:
http://www.mail-archive.com/dev@mesos.apache.org/msg20729.html
The general plan I have for implementing this:
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).
> Remove --checkpoint flag in the slave once checkpointing is stable.
> -------------------------------------------------------------------
>
> Key: MESOS-444
> URL: https://issues.apache.org/jira/browse/MESOS-444
> Project: Mesos
> Issue Type: Task
> Reporter: Benjamin Mahler
> Assignee: Cody Maloney
> Labels: newbie
>
> In the interim of slave recovery being worked on (see: MESOS-110), we've
> added a --checkpoint flag to the slave to enable or disable the feature.
> Prior to releasing this feature, we need to remove this flag so that all
> slaves have checkpointing available, and frameworks can choose to use it.
> There's no need to keep this flag around and add configuration complexity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
