Re: CPU resource allocation: ignore?

2015-03-11 Thread Connor Doyle
(*):22974 (total allocatable: ports(*):[31000-32000, 80-443]; cpus(*):2; mem(*):1979; disk(*):22974) on slave 20150311-150951-3982541578-5050-50860-S0 from framework 20150311-150951-3982541578-5050-50860- And mesos master UI is showing both CPU and MEM resources status. Btw, we

Re: CPU resource allocation: ignore?

2015-03-11 Thread Geoffroy Jabouley
*; mem(*):1979; disk(*):22974 (total allocatable: ports(*):[31000-32000, 80-443]; *cpus(*):2*; mem(*):1979; disk(*):22974) on slave 20150311-150951-3982541578-5050-50860-S0 from framework 20150311-150951-3982541578-5050-50860- And mesos master UI is showing both CPU and MEM resources status

Re: CPU resource allocation: ignore?

2015-03-11 Thread Ian Downes
(*):1979; disk(*):22974 (total allocatable: ports(*):[31000-32000, 80-443]; *cpus(*):2*; mem(*):1979; disk(*):22974) on slave 20150311-150951-3982541578-5050-50860-S0 from framework 20150311-150951-3982541578-5050-50860- And mesos master UI is showing both CPU and MEM resources status

Re: mesos-collectd-plugin

2015-03-11 Thread Dick Davies
Hi Dan I can see a couple of things that could be wrong (NB: not a collectd expert, but these are differences I see from my working config). 1. Is /opt/collectd/etc/collectd.conf your main collectd config file? otherwise, it's not being read at all by collectd. 2. I configure the plugin in

Re: mesos-collectd-plugin

2015-03-11 Thread Dan Dong
Hi, Dick, 1. Yes, /opt/collectd/etc/collectd.conf is my main and only collectd config file. 2. Have put the Module mesos-master block into collectd.conf now. 3. I have set only 1 master, and set the Host line to ip address of master node and restarted collectd. I think I have to install

Call for MesosCon 2015 Sponsors

2015-03-11 Thread Chris Aniszczyk
Hello Mesos community! We're in the process of planning MesosCon 2015 http://events.linuxfoundation.org/events/mesoscon for this August and are super thankful to our current list of sponsors: Cisco, eBay, Hubspot, Mesosphere, Twitter and VMWare. We are still looking for sponsors! if you're

Re: mesos on coreos

2015-03-11 Thread Gurvinder Singh
Thanks Alex for the information and others too for sharing their experiences. - Gurvinder On 03/11/2015 07:50 PM, Alex Rukletsov wrote: Gurvinder, no, there are no publicly available binaries, neither is documentation at this point. We will publish either or both as soon as it is rock solid.

Re: CPU resource allocation: ignore?

2015-03-11 Thread Ben Whitehead
*from the master:* I0311 15:15:16.764714 50884 hierarchical_allocator_process.hpp:563] Recovered ports(*):[31000-32000, 80-443]; *cpus(*):2*; mem(*):1979; disk(*):22974 (total allocatable: ports(*):[31000-32000, 80-443]; *cpus(*):2*; mem(*):1979; disk(*):22974) on slave 20150311-150951-3982541578

Re: mesos on coreos

2015-03-11 Thread Gurvinder Singh
On 03/10/2015 11:41 PM, Tim Chen wrote: Hi all, As Alex said you can run Mesos in CoreOS without Docker if you put in the dependencies in. Tim, is there any documentation of using Mesos outside container in CoreOS available or binary available which we can wget in cloud-init file to fulfill

Re: Question on Monitoring a Mesos Cluster

2015-03-11 Thread Alex Rukletsov
The master/cpus_percent metric is nothing else than used / total. It however represent resources allocated to tasks, but tasks may not use them fully (or use more if isolation is not enabled). You can't get actual cluster utilisation, the best option is to aggregate system/* metrics, that report

Re: mesos on coreos

2015-03-11 Thread Adam Bordelon
Some current issues are listed under https://issues.apache.org/jira/browse/MESOS-2115 See also previous email discussions: http://www.mail-archive.com/user%40mesos.apache.org/msg02123.html http://www.mail-archive.com/user%40mesos.apache.org/msg01617.html On Tue, Mar 10, 2015 at 4:58 PM, craig w

Re: CPU resource allocation: ignore?

2015-03-11 Thread Geoffroy Jabouley
-443]; *cpus(*):2*; mem(*):1979; disk(*):22974 (total allocatable: ports(*):[31000-32000, 80-443]; *cpus(*):2*; mem(*):1979; disk(*):22974) on slave 20150311-150951-3982541578-5050-50860-S0 from framework 20150311-150951-3982541578-5050-50860- And mesos master UI is showing both CPU and MEM