Having invested further, it appears as though our framework is indeed receiving
multiple offers, but discounting 2 out of 3 because of a bug we have. My
apologies for the noise.
Kind regards,
Christopher
Christopher Hunt
Technical Lead, Lightbend Production Suite
@huntchr
UTC+10
On Sun, Nov 27, 2016 at 7:53 PM, Christopher Hunt <
christopher.h...@lightbend.com> wrote:
> My question here though is in the event of receiving a resource offer with
> no CPU in it, and then declining it, why shouldn’t my framework receive
> offers regarding other nodes with CPU? Surely a
> do you mean, you *never* receive updates about other nodes or you just don't
> receive them regularly? If you receive an offer initially and you don't
> accept or decline it, you will not receive that offer again. You can cache it
> for some time locally and then accept it at a later point in
Hi Christopher,
do you mean, you *never* receive updates about other nodes or you just
don't receive them regularly? If you receive an offer initially and you
don't accept or decline it, you will not receive that offer again. You can
cache it for some time locally and then accept it at a later
Hi there,
I’ve been using Mesos for a few months now and I’m a little mystified by Mesos
sending my framework resource offers with no CPU in them.
I cannot see much utility of Mesos sending such resource offers, but that
aside, if my framework declines them then why doesn’t Mesos send resource
5 matches
Mail list logo
