mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8470) CHECK failure in DRFSorter due to invalid framework name.
Date Wed, 08 Aug 2018 18:58:00 GMT

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

Benjamin Mahler commented on MESOS-8470:
----------------------------------------

The master should invalidate any custom framework IDs like this before it enters the allocator.

> CHECK failure in DRFSorter due to invalid framework name.
> ---------------------------------------------------------
>
>                 Key: MESOS-8470
>                 URL: https://issues.apache.org/jira/browse/MESOS-8470
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation
>            Reporter: Chun-Hung Hsiao
>            Priority: Major
>              Labels: allocator, mesosphere
>
> A framework registering with a custom {{FrameworkID}} containing slashes such as {{/foo/bar}}
will trigger a CHECK failure at https://github.com/apache/mesos/blob/177a2221496a2caa5ad25e71c9982ca3eed02fd4/src/master/allocator/sorter/drf/sorter.cpp#L167:
> {noformat}
> master.cpp:6618] Updating info for framework /foo/bar 
> sorter.cpp:167] Check failed: clientPath == current->clientPath() (/foo/bar vs. foo/bar)
> {noformat}
> The sorter should be defensive with any {{FrameworkID}} containing slashes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message