[jira] [Commented] (MESOS-6110) Deprecate using health checks without setting the type

["Silas Snider (JIRA)" <ji...@apache.org>]

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

Silas Snider commented on MESOS-6110:
-------------------------------------

Hmm, this is confusing. Since this is an API change, I believe that we have to wait until 2.0 is cut to deprecate it, and then we have to wait 6 months before removing it. Is this what you mean?

> Deprecate using health checks without setting the type
> ------------------------------------------------------
>
>                 Key: MESOS-6110
>                 URL: https://issues.apache.org/jira/browse/MESOS-6110
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.1.0
>            Reporter: Silas Snider
>            Assignee: haosdent
>            Priority: Blocker
>              Labels: compatibility, health-check, mesosphere
>
> When sending a task launch using the 1.0.x protos and the legacy (non-http) API, tasks with a healthcheck defined are rejected (TASK_ERROR) because the 'type' field is not set.
> This field is marked optional in the proto and is not available before 1.1.0, so it should not be required in order to keep the mesos v1 api compatibility promise.
> For backwards compatibility temporarily allow the use case when command health check is set without a type.



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