Go ahead and use TaskStatus.data; that's what it's there for, although at some point you may need to make the data itself a serialized object if we need to communicate multiple fields. Adding new fields to TaskStatus itself would require a change in Mesos proper, which could take a while. However, it could be useful to add a general key-value "labels" map to TaskStatus to help frameworks that do want to pass info back.
On Fri, Mar 27, 2015 at 9:42 AM, Paul Read <[email protected]> wrote: > <https://github.com/mesos/myriad> Mapping NM NodeId to Mesos TaskId > > Having studied the problem I think I'm ready to implement a solution. There > are two ways, that I can see, of transporting the NM id to the scheduler. > The first would be to coop the TaskStatus "data" field which does not > appear to be used either in myriad or mesos or a better way would be to add > either a "sub_task" field or a "child" field to the TaskStatus structure. > > Since this is a mesos baseline issue and not a myriad issue I would like > the thoughts of those better positioned to make this decision. > > Thanks > > Paul >
