[
https://issues.apache.org/jira/browse/MESOS-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228929#comment-15228929
]
Zhitao Li commented on MESOS-5030:
----------------------------------
[~bmahler], I noticed that there is already a {{message Task}} defined in
src/messages/messages.proto, although it has been in mesos::internal namespace
and not exposed.
My understanding is that I should not try to reuse this message for the purpose
of this task, but rather define new message and afford several lines of
{{CopyFrom}} code. Please let me know if I'm not getting it right.
Thanks.
> Expose TaskInfo's metadata to ResourceUsage struct
> --------------------------------------------------
>
> Key: MESOS-5030
> URL: https://issues.apache.org/jira/browse/MESOS-5030
> Project: Mesos
> Issue Type: Improvement
> Components: oversubscription
> Reporter: Zhitao Li
> Assignee: Zhitao Li
> Labels: qos, uber
>
> So QosController could use metadata information from TaskInfo.
> Based on conversations from Mesos work group, we would at least include:
> - task id;
> - name;
> - labels;
> ( I think resources, kill_policy should probably also included).
> Alternative would be just purge fields like `data`.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
