[MESOS-2875] Add containerId to ResourceUsage to enable QoS controller to target a container

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.25.0
• Fix Version/s: 0.25.0
• Component/s: agent, oversubscription
• Labels: race-condition slave
• Target Version/s: 0.25.0
• Assignee: Klaus Ma
• Reporter: Niklas Quarfot Nielsen
• Shepherd: Niklas Quarfot Nielsen
• Created: 16/Jun/15 18:02
• Updated: 18/Sep/15 00:00
• Resolved: 17/Sep/15 22:45

Description

We should ensure that we are addressing the container which the QoS controller intended to kill. Without this check, we may run into a scenario where the executor has terminated and one with the same id has started in the interim i.e. running in a different container than the one the QoS controller targeted.

This most likely requires us to add containerId to the ResourceUsage message and encode the containerID in the QoS Correction message.