You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@mesos.apache.org by Christoph Heer <ch...@thelabmill.de> on 2017/08/28 16:59:11 UTC

TaskStatus.uuid for idempotent status handling

Hi,

as described in Mesos' documentation [1], a framework scheduler should 
handle status updates idempotent.
Would it be sufficient to store the uuid of the status update and ignore 
retransmissions with the same uuid?
Based on Mesos master and agent logs the uuid is stable across 
retransmissions but I couldn't found a statement which confirms my 
assumption.

Thank you in advance.

Best regards,
Christoph

[1] 
http://mesos.apache.org/documentation/latest/high-availability-framework-guide/

Re: TaskStatus.uuid for idempotent status handling

Posted by Benjamin Mahler <bm...@apache.org>.

Yes, the UUID is how you would check for a duplicate due to
re-transmission. These duplicates still need to be acknowledged.

Ben

On Mon, Aug 28, 2017 at 9:59 AM, Christoph Heer <ch...@thelabmill.de>
wrote:

> Hi,
>
> as described in Mesos' documentation [1], a framework scheduler should
> handle status updates idempotent.
> Would it be sufficient to store the uuid of the status update and ignore
> retransmissions with the same uuid?
> Based on Mesos master and agent logs the uuid is stable across
> retransmissions but I couldn't found a statement which confirms my
> assumption.
>
> Thank you in advance.
>
> Best regards,
> Christoph
>
> [1] http://mesos.apache.org/documentation/latest/high-availabili
> ty-framework-guide/
>