You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "James DeFelice (JIRA)" <ji...@apache.org> on 2017/11/03 15:18:00 UTC
[jira] [Created] (MESOS-8169) master validation incorrectly rejects
slaves, buggy executorID checking
James DeFelice created MESOS-8169:
-------------------------------------
Summary: master validation incorrectly rejects slaves, buggy executorID checking
Key: MESOS-8169
URL: https://issues.apache.org/jira/browse/MESOS-8169
Project: Mesos
Issue Type: Bug
Affects Versions: 1.4.0
Reporter: James DeFelice
Priority: Major
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:
{code}
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'
{code}
(yes, "default" is probably a terrible name for an ExecutorID - that's a separate discussion!)
/cc [~neilc]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)