You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Silas Snider (JIRA)" <ji...@apache.org> on 2016/08/30 22:40:20 UTC
[jira] [Updated] (MESOS-6110) TASK_ERROR because of HealthCheck
when using 1.1.0
[ https://issues.apache.org/jira/browse/MESOS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Silas Snider updated MESOS-6110:
--------------------------------
Description:
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.
was:
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 compatibility consistent.
> TASK_ERROR because of HealthCheck when using 1.1.0
> --------------------------------------------------
>
> 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: Alexander Rukletsov
> Priority: Blocker
> Labels: compatibility, health-check
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)