One ugly way [because it's not centralized] is to code each TC for a preferred SRS. The problem with this approach is that SRS's own load balancing algorithm might override this.
For example, I could hard-code my TC to go to SRS1 of the FOG but once the TC gets to SRS1, the SunRay software may decide that SRS1 is too heavily loaded and transfer the session to SRS2 or 3. I would query the customer as to why he wants to do this: what benefit does he think he's getting? Does he not have faith in the SRS load balancing? Scott -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robert Jaudon Sent: Friday, July 02, 2010 10:02 AM To: [email protected] Subject: EXTERNAL:[SunRay-Users] Question on Load Balancing I have a customer that has a 3 server FOG setup. Per the customers request they want to move a certain number of Sunray's onto each secondary server and have them remain there no matter what. The only way I know how to make a DTU stick on a particular server is to take the opposing server offline. I know that is not proper and did some researching and found via the auth.props file you can set enableLoadBalancing to false which kills the load balancing effect. What are the cons for doing this? Will replication be affected? Are there any other ways I can accomplish having the DTU's stick on a specific server and not load balance? -- Thank you, Robert Jaudon _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
