Ian Cunningham wrote:
I have tried out 3.0.0 on windows. I had to edit the confuse/tests makefile to get it to compile. The default gmond.conf has setuid = yes, which causes gmond to fail on start. The installer works nice too.I played around with sending unicast UDP to another gmond (that was on multicast as well), and when it was set to receive on that unicast channel it saw the unicast gmond, but it didn't tell anyone else in the multicast channel about that host. I assume this is because all that it sends on the multicast channel is updates about itself.
we will have proxy messaging in future releases of ganglia. you're right... it might be nice for a gmond that gets a unicast message to share it with its multicast buddies (if it has any). we'll just have a ttl for unicast messages that ensures the forwarding only goes as far as you want it too.
So now the weird part. If the unicast gmond doesn't have itself
listening to itself, it doesn't know about itself. So if I have the
following:
udp_send_channel {
host = 127.0.0.1
port = 8679
}
/*udp_recv_channel {
port = 8679
}*/
(or vice versa) and I query the tcp port, ganglia knows nothing
interesting. This is what you would expect. But it blows my mind that a
unicast gmond doesn't share data about itself, with itself, unless
explicitly stated. I think this is the correct behavior, but it is hard
to understand at first.
thanks for the feedback. we'll have to keep that in mind for others as they install it. to be honest, i should disable loopback for multicast as well.... i think it's best to make everything explicit. somewhere out there a person might want to have gmond's left hand not know what the right hand is doing. :)
-matt
--
PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3'
They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety.
--Benjamin Franklin, Historical Review of Pennsylvania, 1759
signature.asc
Description: OpenPGP digital signature
