mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8169) master validation incorrectly rejects slaves, buggy executorID checking
Date Fri, 03 Nov 2017 15:18:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237734#comment-16237734
] 

ASF GitHub Bot commented on MESOS-8169:
---------------------------------------

Github user jdef commented on the issue:

    https://github.com/apache/mesos/pull/248
  
    https://issues.apache.org/jira/browse/MESOS-8169


> 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
>              Labels: mesosphere
>
> 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)

Mime
View raw message