Hi Alan,

At the moment we haven’t had to use stick tables / sticky sessions to handle 
authentication. The way our front end load balancing works at the moment is by 
using IP redirection:


  *   All external users are directed to a specific front end
  *   We have another one for internal users only, e.g. our teams processing 
submissions
  *   We have a list of whitelisted bots that are all directed to a third front 
end instance

Our limitation is now mostly with the backend, as we only have one at present, 
and we occasionally experience performance issues under very heavy traffic, but 
it is mostly OK.

We would love to investigate next how to achieve load balancing with multiple 
backend, but that one I guess becomes much trickier so I would love hear from 
other that have experience with it, or thoughts about it.

Best,
Agustina

From: Alan Orth <alan.o...@gmail.com>
Date: Tuesday, 9 January 2024 at 07:28
To: Agustina Martinez-Garcia <am...@cam.ac.uk>
Cc: DSpace Technical Support <dspace-tech@googlegroups.com>
Subject: Re: [dspace-tech] Re: How to set up load balance?
Dear Augustina,

This sounds very interesting. We have a large self-hosted repository with many 
users as well, and I'm thinking that we will need to do something similar in 
the future. I would love to hear more about your setup. In particular, how does 
load balancing handle authenticated users? I'm thinking through this now... 
maybe it's not an issue because Angular itself doesn't care about the session 
per se. Only the backend API and the client care about sessions.

Thanks,

On Thu, Dec 21, 2023 at 6:13 PM Agustina Martinez-Garcia 
<am...@cam.ac.uk<mailto:am...@cam.ac.uk>> wrote:
Hi Jack,

The information from the DCAT notes is not fully correct. This is the setup 
that we have:

- We have 3 frontend VMs, and load balancing is achieved through HAProxy
- We have a single VM for the backend (single tomcat)
- A separate VM for Solr

I hope that clarifies.

Best,
Agustina

On Thursday 21 December 2023 at 13:09:13 UTC Jack OE wrote:
Hi all,

I discovered on this page that Shannon Searle mentioned Cambridge has set up 
load balance for their servers:
https://wiki.lyrasis.org/display/cmtygp/DCAT+Meeting+September+2023

"Shannon Searle:

Cambridge had some issues with slow connectors - they have a large self-hosted 
repository. They have a separate Angular interface for staff/students and 
another for public, a separate solr server and two backend tomcat servers with 
a round-robin  load balance"

How did they achieve load balance and how would I go about setting it up?

Any help is appreciated
Thanks

Jack
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/3cb6f481-8192-430f-9eb9-85838c32e9e9n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/3cb6f481-8192-430f-9eb9-85838c32e9e9n%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
Alan Orth
alan.o...@gmail.com<mailto:alan.o...@gmail.com>
https://picturingjordan.com<https://picturingjordan.com/>
https://englishbulgaria.net<https://englishbulgaria.net/>
https://mjanja.ch<https://mjanja.ch/>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/LO2P265MB31043D77F431577F5A3F6256BF6A2%40LO2P265MB3104.GBRP265.PROD.OUTLOOK.COM.

Reply via email to