Andy Brody wrote:
>Ah, so I can't use just one head node gmond to receive data from
>different clusters. Oh well...
>
>
Actually, you can.
We have an arrangement where we have several clusters arranged in
several grids all reporting into one machine. We use unicast from each
machine to a single "central" machine which runs distinct gmond's for
each cluster and gmetad's for each grid, all on different ports. The
trick is that you can configure the gmond's on that central system not
to collect any metrics from the local machine. It "belongs" to exactly
one of the clusters. Here's a sample gmond.conf from one of the
clusters on that head node. This cluster is named "cluster 1", and
belongs to the "infrastructure" grid. (I notice that we have a
udp_send_channel{} phrase in here; I'm not certain that we need it...
Oh, I remember: we were going to have a duplicate "central machine", and
wanted the gmond's on both of those machines to share. Consider this
aspect a partially formed thought.)
central_machine$ cat gmond.cluster1.conf
/* Generated via setup and m4 */
/* This configuration is as close to 2.5.x default behavior as possible
The values closely match ./gmond/metric.h definitions in 2.5.x */
globals {
daemonize = yes
setuid = yes
user = nobody
debug_level = 0
max_udp_msg_len = 1472
mute = no
deaf = no
host_dmax = 604800 /*secs; 7 days */
cleanup_threshold = 300 /*secs */
gexec = no
}
/* If a cluster attribute is specified, then all gmond hosts are wrapped inside
* of a <CLUSTER> tag. If you do not specify a cluster tag, then all <HOSTS>
will * NOT be wrapped inside of a <CLUSTER> tag. */
cluster {
name = "Cluster 1"
owner = "us"
latlong = "unspecified"
url = "http://central_machine/ganglia/infrastructure";
}
/* The host section describes attributes of the host, like the location */
host {
location = "Our City"
}
/* Feel free to specify as many udp_send_channels as you like. Gmond
used to only support having a single channel */
/*
udp_send_channel {
mcast_join = 239.2.11.71
port = 8640
ttl = 1
}
*/
/* You can specify as many udp_recv_channels as you like as well. */
udp_recv_channel {
port = 8640
}
/* You can specify as many tcp_accept_channels as you like to share
an xml description of the state of the cluster */
tcp_accept_channel {
port = 8640
}
/* NO collections here. We are listening and aggregating other systems.
We're not even in this cluster!
*/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
