yes, it's also happening for me on 3.3.1
Anyone know how to move forward with this? I'd consider this a quite
serious issue.
Cheers,
Florian
On 12.03.12 18:46, Wiebalk, John wrote:
> We are also experiencing this issue at our site. We are running Ganglia
> 3.2 on AIX. We recently upgrade from
Can you please try the following if possible:
1) Run gmond without any additional modules and check if it is still
leaking memory.
--> This test would exclude - if gmond is then still leaking memory -
any additional gmond module as the culprit for the memory leak.
2) Do you have the chance to r
My gmond's always bloat quite large. To combat this, I've dedicated a
single host with massive amount of swap to run a gmonds as a
'collector' role. Every time I add a new cluster, I add a new gmond
instance on the collector box with a new port.
The recent discussion about setting dmax caused me t
On Mar 20, 2012, at 12:02 PM, David Birdsong wrote:
> My gmond's always bloat quite large. To combat this, I've dedicated a
> single host with massive amount of swap to run a gmonds as a
> 'collector' role. Every time I add a new cluster, I add a new gmond
> instance on the collector box with a n
Did you try ganglia-modules-linux ?
http://gmod-linux.sourceforge.net/
On 10/03/12 20:39, Ozzie Sabina wrote:
> On Mar 10, 2012, at 2:20 PM, Vladimir Vuksan wrote:
>
>> What file system metrics are you looking for ? Core python modules collect
>> metrics from
>> ...
>>
> Actually I'm m
5 matches
Mail list logo