On 1/10/2011 at 4:52 PM, in message
aanlktinbmlmnbcti3q-sjuocmp=+igaggo0trj3gf...@mail.gmail.com, Bernard Li
bern...@vanhpc.org wrote:
Hi Brad:
Thanks for your reply.
On Mon, Jan 10, 2011 at 8:06 AM, Brad Nicholes bnicho...@novell.com wrote:
The purpose of setting the
On Mon, 10 Jan 2011 15:52:50 -0800, Bernard Li bern...@vanhpc.org wrote:
I have a perhaps naive question. It sounds like
send_metadata_interval is only relevant to unicast configuration, so
why is multicast affected as well? How difficult of a code change
would it be if we make the
Hi Brad:
On Tue, Jan 11, 2011 at 7:33 AM, Brad Nicholes bnicho...@novell.com wrote:
Actually I think this is a good idea. In my experience, unicast seems to be
more the norm rather than the exception now. If we were to make unicast the
default, then that would make the suggestion above
On 1/7/2011 at 9:10 PM, in message
aanlktikfk_hy2v_zvkb_pra6vxmeqnv3nw3iokhxx...@mail.gmail.com, Jesse Becker
haw...@gmail.com wrote:
On Fri, Jan 7, 2011 at 15:25, Bernard Li bern...@vanhpc.org wrote:
Hi all:
Since the release of Ganglia 3.1, we have introduced the new
configuration option
Hi Brad:
Thanks for your reply.
On Mon, Jan 10, 2011 at 8:06 AM, Brad Nicholes bnicho...@novell.com wrote:
The purpose of setting the send_metadata_interval to 0 by default was to
avoid unnecessary traffic for our default configuration of multicast.
Setting the directive to anything other
On Fri, 7 Jan 2011 23:10:06 -0500, Jesse Becker haw...@gmail.com wrote:
I think that it's fine to set this to a non-zero value, but I wonder
if 30 seconds is too high. I did a quick set of checking on the
actual packets that are sent--and specifically the metadata packets.
I haven't been
On Fri, Jan 7, 2011 at 15:25, Bernard Li bern...@vanhpc.org wrote:
Hi all:
Since the release of Ganglia 3.1, we have introduced the new
configuration option send_metadata_interval in gmond.conf. This is
set to 0 by default and the user must set this to a sane number if
using unicast
