I am using what I think to be a fairly standard gmond.conf:
globals {
daemonize = yes
setuid = yes
user = nobody
debug_level = 0
max_udp_msg_len = 1472
mute = no
deaf = no
allow_extra_data = yes
host_dmax = 86400 /*secs. Expires (removes from web interface) hosts in 1 day
*/
host_tmax = 30 /*secs */
cleanup_threshold = 300 /*secs */
gexec = no
send_metadata_interval = 30 /*secs */
}
cluster {
name = "MDACC"
owner = "MD Anderson Caner Center"
latlong = "unspecified"
url = "unspecified"
}
host {
location = "8,3,1"
}
udp_send_channel {
host = cnode340
port = 8649
}
udp_recv_channel {
port = 8649
retry_bind = true
}
tcp_accept_channel {
port = 8649
}
gmetad is set to check every 60 seconds:
data_source "MDACC" 60 cnode340:8649
Everything works well until around 200 hosts where it appears gmetad starts
having issues. I have ~340 hosts to go in to this cluster. Should I be running
multiple gmetads for this amount of hosts? With all of them active the web
interface reports all of them down and collects no stats at all. I am looking
for advice on getting this up and running properly. The ganglia host isn't
underpowered at all IMO and has plenty of HDD space:
Mem: 32955788 (from free)
16 Cores (AMD Opteron(tm) Processor 6128)
Thanks for any assistance.
Respectfully,
Mark L. Potter
Research IS & Technology Services
UNIX Systems Administrator
O: 713-745-2032
C: 713-965-4133
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
