Re: Mesos making offers for no CPU
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
Re: Mesos making offers for no CPU
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 resource offer declination > is an indicator that the particular node in question isn’t suitable and > Mesos should move on… > You should receive offers from other nodes. Are there other frameworks in your cluster that are starving out this framework? Can you see (and paste it here) master logs to see who are being sent offers for other nodes?
Re: Mesos making offers for no CPU
> 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. I understood that it was good practice to either accept or decline an offer, and not store them up… I don’t recall where I received that advice from now, but it feels like the right thing to do. 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 resource offer declination is an indicator that the particular node in question isn’t suitable and Mesos should move on… Thanks. Kind regards, Christopher Christopher Hunt Technical Lead, Lightbend Production Suite @huntchr UTC+10
Re: Mesos making offers for no CPU
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 < christopher.h...@lightbend.com> 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 > >
Mesos making offers for no CPU
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
