Setting Up High Availability Cluster in AWS
TLDR Retheesh needed help setting up a high availability cluster in AWS. Jason recommended using EC2 instances and provided instructions for setting up typesense nodes.
1
Jul 09, 2023 (3 months ago)
Retheesh
06:36 PMIs there any guidance or example available for setting up a high availability cluster in AWS?
I understand from the high availability documentation we need to provide the node IP addresses and peer ports as part of configuration
• I was checking if this is possible in ECS, but seems its not easy as the tasks cannot communicate each other in ECS (dynamic ips in ENI, not sure bridge network might help across hosts).
• Another work around may be create multiple services in ECS with single task and using service discovery and which seems not clean any may become costly
• The only other option I am seeing is individually provision ec2 instances and manually configure each ec2 instances for cluster. Also may be setup a docker swarm using same instances
Can anyone advise here. Is there some simpler or recommended way? Is there also some AWS AMIs available to easily spawn up an ec2 typesense node with necessary configurations?
Jason
08:00 PMSo the best way to deploy Typesense on AWS IMO would be to just use EC2 instances
Jason
08:01 PMJul 10, 2023 (3 months ago)
Retheesh
07:41 AMAlso one more doubt like how much time it takes to reload all the index to in memory from the drive if we restart typesense any time.
1
Jason
04:22 PMTypesense
Indexed 2786 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Cluster Sync Issues in K8s Environment
Robert encountered node syncing issues in the K8s cluster with Typesense nodes. Kishore Nallan offered advice, including using DNS names and suggesting a call. Robert plans to use a single region Typesense with Redis caching. The thread resolved with the possibility of configuring Typesense with DNS names from 0.21.0.
Addressing Typesense Server Issues and Optimization Needs
Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.
Optimizing Typesense Implementation for Large Collections
Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.