On Mon, 2015-02-02 at 08:47 +0100, Geoffroy Jabouley wrote:
> Hello
>
>
> let's have a look at the message displayed in Jenkins log:
>
> INFO: Offer not sufficient for slave request:
> [name: "cpus"
> type: SCALAR
> scalar {
> value: 1.6
> }
> role: "*"
>
> ==> The Mesos slave is currently offering 1.6 CPU resources
>
> name: "mem"
> type: SCALAR
> scalar {
> value: 455.0
> }
> role: "*"
> ==> The Mesos slave is currently offering 455MB of RAM resources
>
>
> name: "disk"
> type: SCALAR
> scalar {
> value: 32833.0
> }
> role: "*"
> ==> The Mesos slave is currently offering 32GB of Disk resources
>
> , name: "ports"
> type: RANGES
> ranges {
> range {
> begin: 31000
> end: 32000
> }
> }
> role: "*"
> ==> The Mesos slave is currently offering ports between 31000 & 32000
> (default)
>
> ]
> []
> Requested for Jenkins slave:
> cpus: 0.2
> mem: 704.0
>
>
>
> ==> Your Jenkins slave is requesting 0.2 CPU and 704 MB of RAM
>
>
>
> So for me it is normal that your Jenkins slave request cannot be
> fullfilled by Mesos, at least by this mesos slave, as it only has
> 455MB of RAM to offer and you need 704MB.
Hi Geoffroy,
Thanks for taking the time to explain this but I think I'm getting more
confused.
These slaves are all single-tasked as far as Jenkins is concerned -
there is only 1 executor per slave so a slave should not (surely) be
offered if it's already running a job. They all have 3Gb RAM so I don't
know how a slave could have only 455Mb RAM available.
The jenkins plugin settings are set to the defaults:
Jenkins Slave CPUs 0.1
Jenkins Slave Memory in MB 512
Maximum number of Executors per Slave 1
Jenkins Executor CPUs 0.1
Jenkins Executor Memory in MB 128
... whatever all that means!! And why would it be requesting 704Mb and
0.2 CPUs? Where do those numbers come from? Adding "Jenkins Slave Memory
in MB" and "Jenkins Executor Memory in MB" comes to 640Mb
Thanks
Bob
>
>
> FYI, the requested memory for a Jenkins slave is derived from the
> following calculation: Jenkins Slave Memory in MB + (Maximum number of
> Executors per Slave * Jenkins Executor Memory in MB).
> Maybe that's why you are seeing 704MB here and not 512MB as expected.
>
>
>
>
> But if you have several other Mesos slaves each offering 2CPU/2GB RAM,
> then this should not be a problem and the Jenkins slave should be
> created on another Mesos slave (log message is something like "offers
> match")
>
>
>
> Are there any other "apps" running on your Mesos slave (another
> jenkins slave, a jenkins master, ...) that would consume missing
> resources?
>
>
>
>
> 2015-02-02 6:11 GMT+01:00 Hepple, Robert <rhep...@tnsi.com>:
> On Sun, 2015-02-01 at 21:02 -0800, Vinod Kone wrote:
> >
> >
> >
> > On Sun, Feb 1, 2015 at 8:58 PM, Vinod Kone
> <vinodk...@gmail.com>
> > wrote:
> > By default mesos slave leaves some RAM and CPU for
> system
> > processes. You can override this behavior by
> --resources flag.
> >
>
> Yeah but ... the slave is reporting 1863Mb RAM and 2 CPUS - so
> how come
> that is rejected by jenkins which is asking for the default
> 0.1 cpu and
> 512Mb RAM???
>
>
> Thanks
>
>
> Bob
>
> > On Sun, Feb 1, 2015 at 6:05 PM, Hepple, Robert
> > <rhep...@tnsi.com> wrote:
> > On Fri, 2015-01-30 at 10:00 +0100, Geoffroy
> Jabouley
> > wrote:
> > > Hello
> > >
> > >
> > > The message means that the received
> resource offer
> > from Mesos cluster
> > > does not meet your jenkins slave
> requirements
> > (memory or cpu). This is
> > > normal message.
> > >
> >
> > ... and here's another thing - the mesos
> master
> > registers the slave as
> > having 2*cpus and 1.8Gb RAM:
> >
> > I0202 11:43:47.623059 25809
> > hierarchical_allocator_process.hpp:442]
> Added slave
> > 20150129-120204-1408111020-5050-10811-S18
> > (ci00bldslv02
> > v.ss.corp.cnp.tnsi.com) with cpus(*):2;
> mem(*):1863;
> > disk(*):32961; ports(*):[31000-32000] (and
> cpus(*):2;
> > mem(*):1863; disk(*):32961;
> > ports(*):[31000-32000] available)
> >
> >
> > --
> > Senior Software Engineer
> > T. 07 3224 9778
> > M. 04 1177 6888
> > Level 20, 300 Adelaide Street, Brisbane QLD
> 4000,
> > Australia.
> >
> > On 18th December 2014, MasterCard acquired
> the Gateway
> > Services business
> > (TNSPay Retail and TNSPay eCommerce) of
> Transaction
> > Network Services, to
> > join MasterCard’s global gateway business,
> DataCash.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Senior Software Engineer
> T. 07 3224 9778
> M. 04 1177 6888
> Level 20, 300 Adelaide Street, Brisbane QLD 4000, Australia.
>
> On 18th December 2014, MasterCard acquired the Gateway
> Services business
> (TNSPay Retail and TNSPay eCommerce) of Transaction Network
> Services, to
> join MasterCard’s global gateway business, DataCash.
>
>
>
>
>
>
>
>
>
>
--
Senior Software Engineer
T. 07 3224 9778
M. 04 1177 6888
Level 20, 300 Adelaide Street, Brisbane QLD 4000, Australia.
On 18th December 2014, MasterCard acquired the Gateway Services business
(TNSPay Retail and TNSPay eCommerce) of Transaction Network Services, to
join MasterCard’s global gateway business, DataCash.
