Typesense Cluster Upgrade Problems and Downtime

How to fix it

Try these in order — the most common fix is first.

1. 1. Typesense Cloud

   Copy steps
   1. Cluster Configuration > Modify, choose the upgrade timeframe, Schedule Change
   2. Enable High Availability for zero downtime upgrades (note HA cannot be turned off once on)
   3. Add all cluster hostnames to your client libraries before the change
   4. You are emailed at the Cluster Alerts address when it finishes
   Did this fix it? Yes No

2. 2. Self-hosted rolling upgrade

   Copy steps
   1. Take a snapshot on the leader
   2. Upgrade one follower, wait for /health to be ok and the node to rejoin as follower
   3. Repeat for the other followers, then stop the leader so a new one is elected and upgrade it last
   4. Check roles with /debug: state 1 is leader, 4 is follower
   Did this fix it? Yes No

3. 3. Prepare

   Copy steps
   1. Read release notes for every version between yours and the target
   2. Test in staging with a set of test searches
   Did this fix it? Yes No

Symptoms

Search is down during an upgrade, a node returns 503 after upgrading, or the cluster does not rejoin as expected.

Why it happens

• Single-node non-HA Cloud cluster has to restart to upgrade (about 5 to 60 minutes, depending on dataset size)
• Client libraries only list one hostname
• Self-hosted nodes upgraded in the wrong order or all at once
• Node still loading data after restart

This guide also covers

• typesense upgrade
• typesense cloud upgrade downtime
• typesense rolling upgrade

Other Typesense errors

• Typesense 503 Not Ready or Lagging Error
• Typesense Out of Memory (OOM) and RAM Sizing
• Typesense Import Error: Field Type Mismatch
• Typesense Schema Update Without Deleting the Collection
• Typesense Search Returning No Results or Missing Typos
• Typesense API Key 401 / 403 Forbidden and Scoped Keys
• Why Is Typesense Slow? High Latency Fixes
• Typesense Cluster Not Working After Node Failure (Quorum Lost)