[torqueusers] too many DNS requests
saydakov at yahoo-inc.com
Mon Feb 13 13:13:30 MST 2006
Thanks for the advice. That is what they did as a temporary measure. But
they don't like the idea of static entries in /etc/hosts. And I don't see
why the server needs to resolve the same address over and over to the point
of overloading the DNS.
From: Lippert, Kenneth B. [mailto:Kenneth.Lippert at alcoa.com]
Sent: Monday, February 13, 2006 11:54 AM
To: Alexander Saydakov; torqueusers at supercluster.org
Subject: RE: [torqueusers] too many DNS requests
As a first step, I would make sure the server has it's own name in it's
/etc/hosts file. I would make sure each client also has the server in it's
/etc/hosts. My cluster is pretty small, so I go ahead and have all clients
and the server listed in all /etc/hosts - that way I never have to bother
the DNS for intra-cluster communications.
Also check that /etc/nsswitch.conf has "files" listed before "dns" under
"hosts" and "networks", so the local /etc/host is read before going to the
From: torqueusers-bounces at supercluster.org
[mailto:torqueusers-bounces at supercluster.org] On Behalf Of Alexander
Sent: Monday, February 13, 2006 2:35 PM
To: torqueusers at supercluster.org
Subject: [torqueusers] too many DNS requests
Currently we are playing with a 33-machine cluster, and our operations folks
started to complain that pbs_server overloads the DNS servers. They say that
it repeatedly resolves its own IP address. There is a pbs_mom running on
that machine also, but since they did not mention requests to resolve other
cluster nodes, I suppose that server<->mom communication is not at fault.
Could it be server<->scheduler communication or something else?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the torqueusers