[
https://issues.apache.org/jira/browse/MESOS-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228629#comment-15228629
]
Anand Mazumdar commented on MESOS-5103:
---------------------------------------
{{TaskHealthStatus}} message is only being used internally by the command
executor code. Another possible solution would be to just move the message from
{{src/messages/messages.proto}} to {{include/mesos/mesos.proto}} (unversioned
internal protobuf) and not add the message to the {{v1}} namespace at all since
there are no external consumers of this message.
> Enhance mesos-health-check to send v1:: TaskHealthStatus message
> ----------------------------------------------------------------
>
> Key: MESOS-5103
> URL: https://issues.apache.org/jira/browse/MESOS-5103
> Project: Mesos
> Issue Type: Bug
> Reporter: Qian Zhang
>
> The existing {{mesos-health-check}}
> (https://github.com/apache/mesos/blob/master/src/health-check/main.cpp) can
> only send the unversioned {{TaskHealthStatus}} message. However, with the new
> Executor HTTP Library, there will be executor which is based on v1 HTTP
> executor API and all the protobuf messages used by it should be v1 as well
> (e.g., {{v1::TaskHealthStatus}}).
> So we may either modify the existing {{mesos-health-check}} binary to send
> {{v1::TaskHealthStatus}} messages in addition to the unversioned ones or
> create a new binary for versioned health checks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
