Hi, you should not post a message with a new subject and topic as replay on this list ;) On Thu, Jul 11, Damian Ohara wrote:
Hi All & Thorsten K.
We're running 12 SuSE NIS slave servers and I'm in the process of upgrading them from 6.4/7.0/7.2 to 8.0.
Unfortunately we have intermittent issues where one machine is hammered by client requests until it's battered into submission. When it stops responding the clients all move to the next-fastest responding NIS server and so on ....
This is still a problem for the SuSE 8.0 servers.
Has anyone looked at a load balancing system for NIS servers or any other solution for clients jumping en-masse to the next server ?
The ypbind load balancing works fine here. It seems your slave servers are in the wrong place of the network. Here, we have always more than one server which is reacheable from the client at the same cost. So if you have 2 slaves in one subnet, every slave has about 50% of the clients, with 3 one 33% (but in worst case our NIS servers are all able to handle the NIS traffic alone). You can try to sort the yp.conf for priority: Use the best server for this client at first and so on. If not all clients have the same yp.conf, they will start searching the fastest server with another server. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B