Hi, So if you have say 4 mid-tiers and 4 remedy-servers and 100 users.
The first load balancer will dirstribute the 100 users to something like 25 per mid-tier server. The load balancer between mid-tiers and the remedy-servers will see only 4 "users", which is the 4 mid-tiers. It is not inpossible that these 4 users might end up with 1 or 2 remedy-servers only if you have a 180 second timeout. If you have 100 real users chatting there will seldom be a 180 second silence on any one mid-tier server, which is what would be required for the mid-tier server to be directed at a new server. Why not do a complete round-robin thing without any 180 second timeout? Best Regards - Misi, RRR AB, http://www.rrr.se (http://www.rrr.se) (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13) * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs Find these products, and many free tools and utilities, at http://rrr.se (http://rrr.se) February 1, 2018 5:03 PM, "Thomas Miskiewicz" wrote: Hey LJ and thank you for the prompt reply. Talked to them already. We’re using round robin. I’m not an expert on LB but my understanding was that we would have about an equal amount of users on all AR Servers using it. The guy explained that once you connect there is a time out of 180 seconds. If you do something within the 180 seconds you will end up on the same server. If you don’t they will balance. Sounds plausible. Any yet what’s the likelihood that people then will be balanced on the second box and not the third. Does anyone there use round robin as well? How do your users get distributed? What are you Mid Tier settings, connection settings in particular? Thomas On Feb 1, 2018, at 4:49 PM, LJ LongWing wrote: Thomas, You'll need to work with the LB team to identify what distribution method they are using....common options are 'round robin' in which it just simply points everything at each server in turn, 'least connections' where it tries to analyze how many are 'currently' connected to each node and send the traffic to the one with the least current load....you'll also want to check and verify that the monitor that you are using to determine if a node is online or not is functioning properly because if the LB monitor says a node is down, it obviously won't send any traffic to it...but if that monitor is faulty, it might be up and running but not reporting as online and can cause the scenario you described... On Thu, Feb 1, 2018 at 8:44 AM, Thomas Miskiewicz wrote:Hi Listers, we got a physical load balancer before the Mid-Tier servers and a logical load balancer between the Mid Tier and our AR Servers. We noticed that on some days all the users land on only one AR Server. On other days two. What’s the reason behind it? What do we need to configure and to enforce equal distribution? Thomas -- ARSList mailing list [email protected] (mailto:[email protected]) https://mailman.rrr.se/cgi/listinfo/arslist (https://mailman.rrr.se/cgi/listinfo/arslist) -- ARSList mailing list [email protected] (mailto:[email protected]) https://mailman.rrr.se/cgi/listinfo/arslist (https://mailman.rrr.se/cgi/listinfo/arslist)
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
