[MESOS-9293] If a framework looses operation information it cannot reconcile to acknowledge updates.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.1, 1.8.0
• Labels: mesosphere operation-feedback
• Target Version/s: 1.7.1
• Epic Link: Resource Provider and CSI Tech Debt
• Sprint: Mesosphere RI-6 Sprint 2018-31, Storage R7 Sprint 33, Storage R8 Sprint 34
• Story Points: 3
• Assignee: Benjamin Bannier
• Reporter: James DeFelice
• Shepherd: Greg Mann
• Created: 04/Oct/18 17:56
• Updated: 14/Dec/18 21:23
• Resolved: 05/Dec/18 22:15

Description

Normally, frameworks are expected to checkpoint agent ID and resource provider ID before accepting an offer with an OfferOperation. From this expectation comes the requirement in the v1 scheduler API that a framework must provide the agent ID and resource provider ID when acknowledging an offer operation status update. However, this expectation breaks down:

1. the framework might lose its checkpointed data; it no longer remembers the agent ID or the resource provider ID

2. even if the framework checkpoints data, it could be sent a stale update: maybe the original ACK it sent to Mesos was lost, and it needs to re-ACK. If a framework deleted its checkpointed data after sending the ACK (that's dropped) then upon replay of the status update it no longer has the agent ID or resource provider ID for the operation.

An easy remedy would be to add the agent ID and resource provider ID to the OperationStatus message received by the scheduler so that a framework can build a proper ACK for the update, even if it doesn't have access to its previously checkpointed information.

I'm filing this as a BUG because there's no way to reliably use the offer operation status API until this has been fixed.

Issue Links

• is related to: MESOS-9455 Add tests for operation status acknowledgement for different combinations of uuid, agent_id and resource_provider_id