[MESOS-8169] Incorrect master validation forces executor IDs to be globally unique.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.4.1, 1.5.0
• Labels: mesosphere
• Flags: Important
• Assignee: James DeFelice
• Reporter: James DeFelice
• Shepherd: James Peach
• Created: 03/Nov/17 15:17
• Updated: 08/Nov/17 16:55
• Resolved: 08/Nov/17 16:24

Description

proposed fix: https://github.com/apache/mesos/pull/248

I observed this in my environment, where I had two frameworks that used the same ExecutorID and then triggered a master failover. The master refuses to reregister the slave because it's not considering the owning-framework of the ExecutorID when computing ExecutorID uniqueness, and concludes (incorrectly) that there's an erroneous duplicate executor ID:

W1103 00:33:42.509891 19638 master.cpp:6008] Dropping re-registration of agent at slave(1)@10.2.0.7:5051 because it sent an invalid re-registration: Executor has a duplicate ExecutorID 'default'

(yes, "default" is probably a terrible name for an ExecutorID - that's a separate discussion!)

/cc neilc

Issue Links

• links to: GitHub Pull Request #248