[jira] [Commented] (MESOS-2546) Mesos 0.20.1 causes framework starvation on single node clusters when using Chronos and Marathon

["Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org>]

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

Niklas Quarfot Nielsen commented on MESOS-2546:
-----------------------------------------------

Hey [~ssk2hd] - can you provide a copy of your state json?

> Mesos 0.20.1 causes framework starvation on single node clusters when using Chronos and Marathon
> ------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-2546
>                 URL: https://issues.apache.org/jira/browse/MESOS-2546
>             Project: Mesos
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 0.20.1
>            Reporter: Sunil Shah
>
> Tracking an issue raised by Chronos users that appears to be a regression in Mesos: https://github.com/mesos/chronos/issues/381#issuecomment-83647539
> 1) Chronos's interval between refusing offers and receiving the next one is at 0.1 seconds to allow finer grained scheduling of jobs.
> 2) On single node clusters running Mesos 0.20.1 with both Chronos and Marathon installed, Marathon did not receive any offers. On multi-node clusters, this behaviour was not observed. This behaviour was not observed when using previous versions of Mesos.
> 3) Changing this interval back to the default value (i.e., by not setting it) fixed this problem. (See [commit|https://github.com/mesos/chronos/commit/fb1ab1c42207b12c8663457d07c322fc81a8ec2e].)
> This can be replicated using an installation of playa-mesos and running both the latest Mesosphere packages of Chronos and Marathon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)