mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Rukletsov <>
Subject Re: Review Request 56215: Reused previous task status to generate a new one in default executor.
Date Thu, 16 Mar 2017 16:45:56 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated March 16, 2017, 4:45 p.m.)

Review request for mesos, Gastón Kleiman and Vinod Kone.

Bugs: MESOS-7249

Repository: mesos

Description (updated)

Sometimes when a new task status update is generated in the executor,
we have to make sure specific data is duplicated from the previous
task status to, e.g., avoid shadowing of these data during
reconciliation. For instance, consider a check status being sent;
in this status update we must include the latest known health

This patch also refactors `update()` routine into two separate calls:
`createTaskStatus()` which is responsible for creating a task status
from scratch and `forward()`, which is responsible for forwarding task
status updates to the agent.

Diffs (updated)

  src/launcher/default_executor.cpp cbd4f7ecd042e7fa603bd69774d95472df2c896d 






Alexander Rukletsov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message