Hi,

I got bitten by the same issue. I was setting task labels but unable to 
retrieve them back through reconciliation.
If a framework can’t read the labels back, what’s the reason labeling tasks at 
first place?

Is there any other mechanism to read task labels that I am missing? Preferable 
through Scheduler API?

I see that the master exposes labels through /state.json but that’s 
terrifiyingly big json blob to deal with.

Thanks,
Altan

On 2016-01-29 12:16 (-0700), Benjamin Mahler <b...@apache.org> wrote: 
> Ah I'm sorry, not sure if the concept of "latest labels" applies in the> 
> same way as "latest health" information for a task, since health is an> 
> active property of the task, whereas labels can be specific to updates.> 
> 
> On Fri, Jan 29, 2016 at 12:09 PM, Benjamin Mahler <bm...@apache.org>> 
> wrote:> 
> 
> > I see that the following was filed:> 
> > https://issues.apache.org/jira/browse/MESOS-4477> 
> >> 
> > But this sounds like a bug: if the master knows about the task during> 
> > reconciliation, labels should be sent. For example we had this same bug 
> > for> 
> > health information:> 
> > https://issues.apache.org/jira/browse/MESOS-2206> 
> >> 
> > On Fri, Jan 22, 2016 at 2:10 PM, Andrii Biletskyi <> 
> > andrii.bilets...@stealth.ly> wrote:> 
> >> 
> >> Okay, thanks for your answer. I will rework my algorithm so it doesn't> 
> >> rely on task labels/data.> 
> >>> 
> >> Thanks,> 
> >> Andrii> 
> >>> 
> >> On Fri, Jan 22, 2016 at 11:49 PM, Vinod Kone <vi...@apache.org>> 
> >> wrote:> 
> >>> 
> >>>> 
> >>> On Fri, Jan 22, 2016 at 1:07 PM, Andrii Biletskyi <> 
> >>> andrii.bilets...@stealth.ly> wrote:> 
> >>>> 
> >>>> 8. Scheduler.statusUpdate callback is called for> 
> >>>> taskId=t1;state=Running. But here I don't receive as part of TaskStatus> 
> >>>> task labels and taskData, they are just empty.> 
> >>>>> 
> >>>> 
> >>> Yea, this is expected behavior. Currently master *generates* new status> 
> >>> updates (with only a few fields set) when it gets a reconciliation 
> >>> request.> 
> >>>> 
> >>> 
> >>> 
> >> 
> 

Reply via email to