Brief Outage During High Availability Cluster Upgrade
TLDR Ed reported an outage during cluster upgrade. Jason suggested it might be due to a 30s delay when a node is unhealthy. Ed confirmed this.
1
Sep 16, 2023 (2 weeks ago)
Ed
09:27 PMJason
10:29 PMJason
10:30 PMEd
10:58 PM<https://v09fm4cjghdr23p7p.a1.typesense.net/multi_search?x-typesense-api-key>
Ed
10:58 PMEd
10:58 PMJason
11:00 PMEd
11:02 PMEd
11:02 PM1
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Troubleshooting Read Timeout Issues on AWS Cluster.
Stefan encountered read timeout issues with AWS cluster, and Kishore Nallan helped evaluate the issue, finding an unhealthy node which was fixed. Kishore Nallan also helped Stefan to upgrade the cluster configuration.
Typesense Cluster Upgrade Issues and Solutions
Ken reported a system outage due to Typesense cluster upgrade issues. Jason recommended upgrading to the next RAM tier and explained when the auto upgrade feature takes effect. After a repeat issue, Jason added handling upgrades when disk space ran out to their backlog.
Upgrading Problems with Typesense Cloud Node
Alan encountered issues with their typesense cloud node during an import, resulting in the need for a manual upgrade. Kishore Nallan assisted with the upgrade process and Jason reported that an upgrade was queued due to a second outage.
Typesense Cloud Cluster Issue and Upgrade Recommendations
Viji reported a cluster issue on Typesense Cloud. Jason identified the cause and recommended upgrading to Typesense 0.24.1 for safeguards against RAM usage spikes.
Troubleshooting Unhealthy Typesense Server
Akash reported a problem with a Typesense server. Kishore Nallan suggested upgrading the CPU limit, upgrading to version 0.23, and changing to a 3 node 2 cpu burst configuration. They also addressed how to increase client timeout.