Load Balancing
Load Balancing test, there are totally seven servers as node. 192.168.1.231 acted as the load balancing server,and the others are really workstations whose ip is from 192.168.1.232 to 192.168.1.237.
238 was the loading server which supply the testing pressure.
First, install MS SQL server 2000 in every realy workstations, and let the sql server startup when completed installation.
The engineer from Nanning decided the strategy of cluster and send commands to our server(231) thought moderm which called remote control. About 40 squel instants was started to connect virtual database (192.168.1.231).
In the 231 machine, I could see the statue about connecing and re-connecting,192.168.1.231 is always the server node,and it distributed the load to the other node such as 192.168.1.232 and/or 192.168.1.233.
There are many strategy in the software which is sent to test in the lab. One strategy is that the PC or customer workstation will always connect to the specific node once it was firstly distributed to the node by the 192.168.1.231. Because some people may do some working in one of the nodes, when the node halted, the data the user are working were not committed, so it perhapes lost. we could not imagine what would happen if the important data lost. this accident need the strategy that ensure custmer always connect to the specific server.
Another strategy is random. The customer’s connect will be distributed to random node. With the count of connecting adds, the loading will be balancing automaticly.
By the way, how to setting the display parameter to 1024×768 in Linux? Only changing the parameter in the display dialog is not enough. Login as root, in the /etc/X11 direction, edit the X1186config file by using vi, find the line including”800×600″ “640 x480”, and insert “1024×768” in this line. saved the file, and logout.
Everything will be ok when login as root again.