Also, everything connected to the same multicast IP is, for all intents and
purposes, on the same cluster... as far as the monitoring core's concerned.
So, if you have three nodes:
1. binky (10.0.0.2)
multicasting on 232.2.72.5
cluster name "work is hell"
2. sheba (10.0.0.3)
multicasting on 232.2.72.5
cluster name "love is hell"
3. bongo (10.0.0.4)
multicasting on 232.2.72.6
cluster name "school is hell"
All three will respond on port 8649.
binky will respond with CLUSTER_NAME="work is hell" and metrics from binky
and sheba.
sheba will respond with CLUSTER_NAME="love is hell" and metrics from binky
and sheba.
bongo will respond with CLUSTER_NAME="school is hell" and metrics from bongo.
Now let's say you add two more:
4. akbar (10.0.0.5)
multicasting on 232.2.72.5
cluster name "akbar & jeff's guide to life"
5. jeff (10.0.0.6)
multicasting on 232.2.72.6
cluster name "akbar & jeff's guide to life"
Now, here's what you get:
binky responds as above, but with metrics from binky, sheba and akbar.
Same with sheba.
bongo responds as above but has metrics from jeff.
akbar responds with CLUSTER_NAME="akbar & jeff's guide to life" and metrics
from binky, sheba and akbar.
jeff responds with CLUSTER_NAME="akbar & jeff's guide to life" and metrics
from bongo and jeff.
gmetad apparently overrides these labels (although the perl one doesn't, I
think?) with whatever you've named in gmetad.conf as the data source names.
So in short, different clusters NEED to use different multicast IPs.
Cluster names are NOT metrics - they are NOT shared amongst all member
nodes (this could change, I guess ... ?), but are specified on each local
host. So if you want the cluster name the same on all nodes, you'll have
to make sure gmond.conf on all nodes has the right name in it.
But it really doesn't matter if you're using gmetad. :)
matt massie wrote:
julien-
http://ganglia.sourceforge.net/ganglia_docs/configuration.html#GMOND-CONFIGURATION
should answer your question. the cluster name is set by the Ganglia
Monitoring Daemon (gmond) in /etc/gmond.conf (by default) with the "name"
parameter. e.g.
name "Cluster in Room 404b"
...
technically you don't need to set the cluster name attribute for all the
gmonds on your cluster.. only the gmonds which are used as a data_source
by gmetad. if you don't set the cluster name the default name is
"unspecified".
-matt
Tomorrow, Julien Leduc wrote forth saying...
Hi all,
I have a problem: I can't set a cluster name to my nodes running gmond,
because the gmetad script takes all the gmond stats on the network so that I
have 4 more machines that are said to be part of my cluster, while these are
just running gmond without any specified cluster name.
Moreover, I have read the documentation, but can't find out were the cluster
name is defined: Gmond or Gmetad, and what is the difference ?
I have a 5 PCs cluster running under Mandrake 8.2 with the ganglia rpm
(containing gmond 2.4.1).
Thanks
Julien Leduc
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
