Hi. New user almost ready to take our first typese...
# community-helpi
Imtiaz Mangerah
10/25/2021, 2:38 AMHi. New user almost ready to take our first typesense system into production. Would just like to thank all the contributors to the project for the amazing work. 🎉
edit: found a bug on my end, solved 🙂
Just had a query with regards to a High Availability setup - I have 3 servers ready to go. I am using the
My questions are:
1. Is this by design - and is there any reason it applies this logic?
2. Would it not be better to share the load between the 3 servers instead of always choosing the first?
3. If sharing the load would benefit the overall performance, is there any API on the client I could use to do this, or should I just randomise the nodes before initialisation?
typesenseImtiaz Mangerah
10/25/2021, 2:48 AMI actually noticed this snippet now:
Copy code
// Attempts to find the next healthy node, looping through the list of nodes once.
// But if no healthy nodes are found, it will just return the next node, even if it's unhealthy
// so we can try the request for good measure, in case that node has become healthy since
getNextNode(requestNumber: number = 0): Node {
...j
Jason Bosco
10/25/2021, 3:07 AM@Imtiaz Mangerah Each instance of the client will round-robin requests between the three nodes.
When you instantiate the client, it will indeed send the first request to Node 1, but subsequent API calls will cause the request to go to Node 2, then Node 3, then Node 1, 2, 3 and so on
Jason Bosco
10/25/2021, 3:10 AMIf you’re not seeing requests go to other nodes, one potential reason could be that the entire client is reinitialized on each request…
👍 1
a
Alex K
11/18/2021, 8:14 PMRegarding node selection is there any attempts at directing traffic to the nearest node geographically?
j
Jason Bosco
11/18/2021, 8:24 PM