Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Wed, 31 Aug 2016 00:14:20 +0000 (UTC)
From: "Michael Gummelt (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.13001519.1472602423000.452571.1472602460428@Atlassian.JIRA>
In-Reply-To: <JIRA.13001519.1472602423000@Atlassian.JIRA>
References: <JIRA.13001519.1472602423000@Atlassian.JIRA> <JIRA.13001519.1472602423598@arcas>
Subject: [jira] [Created] (MESOS-6111) Offer cycle is undocumented
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 31 Aug 2016 00:14:22 -0000

Michael Gummelt created MESOS-6111:
--------------------------------------

             Summary: Offer cycle is undocumented
                 Key: MESOS-6111
                 URL: https://issues.apache.org/jira/browse/MESOS-6111
             Project: Mesos
          Issue Type: Task
          Components: documentation
    Affects Versions: 1.0.1
            Reporter: Michael Gummelt


cc [~neilc]

AFAICT, the "offer cycle" in Mesos is undocumented.  As it has been explained to me, the master will send on offer to a successive list of frameworks ordered by DRF, with a 1s gap in between each offer.  And when the decline timeout (default 5s) is reached, it will start over at the beginning of the list.  This means that, by default, all other frameworks other than the first 5 in DRF ordering will be starved.

I'm going to submit a separate JIRA with a proposal to fix this, but at the very least, we should document the above behavior.


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