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. >
This puzzles me as the jenkins-mesos plugin is only specifying 0.1 CPU and 512Mb RAM. Our slaves have 2Gb RAM each - so they should certainly be 'adequate' - why would they be rejected? How can I make them 'acceptable'? > > > > you can filter logs from specific classes in Jenkins > > 1. from the webUI, in the "jenkins_url"/log/levels panel, set the > logging level for org.jenkinsci.plugins.mesos.JenkinsScheduler > to WARNING > 2. use a logging.properties file > The logs are not what worries us - it's having Jenkins throw a config-history version every time it talks to the mesos master. Also, the mesos slaves often go 'offline' Thanks Bob -- 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.
