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 point in time. Or you decline it and then you will receive the offer again some seconds later. In principle.
Hope that helps, Tobias On Mon, Nov 28, 2016 at 12:31 PM, Christopher Hunt < [email protected]> wrote: > 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 > offers for other nodes where there are resources? As it stands, Mesos > appears to keep sending my framework the same resource offer. This > ultimately fails my framework given that it cannot proceed with launching a > task. > > I can see *why* the resource offer has no CPU - there isn’t any available. > I’m curious to understand why Mesos cannot move on and send resources for > other nodes. > > I’m using DC/OS 1.8 which I believe uses Mesos 1.0. > > Thanks for any info. > > Kind regards, > Christopher > > Christopher Hunt > *Technical Lead, Lightbend Production Suite* > @huntchr > UTC+10 > >
