Jason, You are correct, Jetty running on port 8008, or whatever port they are on certainly needs it's own LB depending on the need of the client in place. If HA is needed, LB makes sense. Regardless of if you are talking about Remedy Restful services or CMDB Restful services...depending on the HA needs of the client/server architecture, LB makes a bunch of sense....the great part about Remedy Restful services is that once you have created a Server Group for Remedy, it's the same server, so not additional hardware :)
On Thu, Feb 1, 2018 at 10:17 AM, Jason Miller <jason.mil...@gmail.com> wrote: > I'll also use this thread as an opportunity for a new discussion related > to load balancing. > > Is anybody aware of any docs that pertain to load balancing Jetty on AR > Server? The REST API has been hosed here for a few years but that wasn't > user-facing (but should be able to setup redundancy). The new CMDB UI is > also using Jetty and this is user-facing (albeit a small user base) so it > is time to start thinking about LB for Jetty. > > It might be straightforward without any special considerations however it > would be very nice to have this setup actually documented for AR > Server/Jetty. > > Jason > > On Thu, Feb 1, 2018 at 10:43 AM, Randeep Atwal <ratwals...@gmail.com> > wrote: > >> From the Mid-Tier side, you also might want to review your setttings as >> described here to work with the load balancer settings: >> >> https://docs.bmc.com/docs/display/public/ars81/Configuring+ >> the+mid+tier+connection+pool >> >> https://docs.bmc.com/docs/brid91/en/configuring-the-mid-tier >> -connection-pool-610403150.html >> >> On Thu, Feb 1, 2018 at 8:16 AM, Aspari Sunil Kumar <sunil.a...@gmail.com> >> wrote: >> >>> There isn't much can be done in mid tier.this is purely LB team need to >>> analyse what is going wrong . Need to sit with them and see why all the >>> connections are going to one server in reality with the help of logs.. we >>> had strange problem recently that on 2 AR servers we used to see same set >>> of users .. we fixed this after lot of analysis with LB team >>> >>> >>> On Feb 1, 2018 7:09 PM, "LJ LongWing" <lj.longw...@gmail.com> wrote: >>> >>> I've always preferred to use least connections personally, but from what >>> I've read of the docs they recommend round robin....but round robin doesn't >>> explain how your LB would be putting everyone on one node...it should >>> literally go 1, 2, 3, 1, 2, 3 for new connections, and as you discussed, >>> keep you on your current server if you are within the timeout, but you >>> should have fairly even load across nodes....do they keep logs of the >>> monitor activity so you can review if the monitor is reporting a server as >>> down during specified periods? What monitor style are you using, ping, >>> tcpip port, something else? >>> >>> On Thu, Feb 1, 2018 at 9:00 AM, Thomas Miskiewicz <tmisk...@gmail.com> >>> 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 <lj.longw...@gmail.com> 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 <tmisk...@gmail.com> >>>> 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 >>>>> ARSList@arslist.org >>>>> https://mailman.rrr.se/cgi/listinfo/arslist >>>>> >>>> >>>> -- >>>> ARSList mailing list >>>> ARSList@arslist.org >>>> https://mailman.rrr.se/cgi/listinfo/arslist >>>> >>>> >>>> >>>> -- >>>> ARSList mailing list >>>> ARSList@arslist.org >>>> https://mailman.rrr.se/cgi/listinfo/arslist >>>> >>>> >>> >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >>> >>> >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >>> >> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> >> > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > >
-- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
