[MESOS-2559] Do not use RunTaskMessage.framework_id.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.24.0
• Component/s: framework
• Labels: mesosphere
• Target Version/s: 0.24.0
• Story Points: 1
• Assignee: Kapil Arya
• Reporter: Kapil Arya
• Shepherd: Adam B
• Created: 26/Mar/15 19:21
• Updated: 26/Nov/18 12:20
• Resolved: 26/Nov/18 12:20

Description

Assume that FrameworkInfo.id is always set and so need to read/set RunTaskMessage.framework_id.

This should land after https://issues.apache.org/jira/browse/MESOS-2558 has been shipped.

Issue Links

• blocks: MESOS-905 Remove Framework.id in favor of FrameworkInfo.id
• blocks: MESOS-2560 Remove RunTaskMessage.framework_id
• is blocked by: MESOS-2557 Do not pass FrameworkID to Framework constructor for Master/Slave.
• is blocked by: MESOS-2558 Mark RunTaskMessage.framework_id as optional
• is blocked by: MESOS-2561 0.23.0 release
• is blocked by: MESOS-2727 0.23.0 Release
• is duplicated by: MESOS-2343 Deprecate framework_id in RunTaskMessage.