[MESOS-2309] Mesos rejects ExecutorInfo as incompatible when there is no functional difference

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.23.0
• Labels: twitter
• Target Version/s: 0.23.0
• Sprint: Twitter Mesos Q1 Sprint 4
• Story Points: 3
• Assignee: Vinod Kone
• Reporter: Zameer Manji
• Shepherd: Till Toenshoff
• Created: 30/Jan/15 23:46
• Updated: 03/Apr/15 22:55
• Resolved: 13/Mar/15 01:30

Description

In AURORA-1076 it was discovered that if an ExecutorInfo was changed such that a previously unset optional field with a default value was changed to have the field set with the default value, it would be rejected as not compatible.

For example if we have an ExecutorInfo with a CommandInfo with the shell attribute unset and then we change the CommandInfo to set the shell attribute to true Mesos will reject the task with:

I0130 21:50:05.373389 50869 master.cpp:3441] Sending status update TASK_LOST (UUID: 82ef615c-0d59-4427-95d5-80cf0e52b3fc) for task system-gc-c89c0c05-200c-462e-958a-ecd7b9a76831 of framework 201103282247-0000000019-0000 'Task has invalid ExecutorInfo (existing ExecutorInfo with same ExecutorID is not compatible).

This is not intuitive because the default value of the shell attribute is true. There should be no difference between not setting an optional field with a default value and setting that field to the default value.

Issue Links

• is related to: AURORA-1076 Docker patch created incompatible ExeuctorInfo changes for GC executor