[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496826#comment-14496826
]
Timothy Chen commented on MESOS-2191:
-------------------------------------
Custom executors I think will need to implement their own logic to gather
whatever it needs when it's in the container, I don't have a good answer for it
yet but so far all the needs are on task containers. Custom executor seems to
be less of a problem as it usually can communicate back to the scheduler
however it wants for information scheduler might need.
Yes current schedulers might not expect it, but since the data message is
controlled by mesos I don't think it will cause any problem and current
schedulers can just ignore the data field. Do you foresee any problems with
this?
> Add ContainerId to the TaskStatus message
> -----------------------------------------
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
> Reporter: Marcel Neuhausler
> Assignee: Alexander Rojas
> Labels: mesosphere
>
> {{TaskStatus}} provides the frameworks with certain information
> ({{executorId}}, {{slaveId}}, etc.) which is useful when collecting
> statistics about cluster performance; however, it is difficult to associate
> tasks to the container it is executed since this information stays always
> within mesos itself. Therefore it would be good to provide the framework
> scheduler with this information, adding a new field in the {{TaskStatus}}
> message.
> See comments for a use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
