#community-help

Server Crash Issue during Search and Solution Discussion

TLDR Chetan reported server crashes after running for 5-10 days, suspecting a container lifetime issue. Jason identified the trouble as a search-caused crash and advised an upgrade to 0.25.0.

1mo

Join the chat

Aug 21, 2023 (1 month ago)

Photo of md5-f5bf390d5711f8a2f96bd93d1bc97d20

Chetan

07:35 PM

my longer-running servers seem to be dying with this error after 5-10 days - is there a standard lifetime a container should be running for before restarts / errors?

Image 1 for my longer-running servers seem to be dying with this error after 5-10 days - is there a standard lifetime a container should be running for before restarts / errors?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:36 PM

No, that’s a crash stack trace during search, which is causing the restart. Could you upgrade to 0.25.0?

Chetan

07:37 PM

have a demo in 23 minutes will do so right after it

Aug 22, 2023 (1 month ago)

Jason

07:38 PM

Hope the demo went ok! 😅

Chetan

10:32 PM

haha thanks - luckily i was saved by some scheduling error, as the server wasn't quite ready yet 😅 but demo early yesterday and this morning went much better!

10:32

Chetan

10:32 PM

now there's actual users using it so i'm setting up proper HA lol.

10:34

Chetan

10:34 PM

thanks for building this, it's pretty awesome. elastic search confused the heck out of me (albeit probably do-able), and algolia would have bankrupted me.

10:34

Chetan

10:34 PM

once i'm making some revenue 😅 definitely want to sign up for one of the support plans at least, you all have way more than earned it with all the help on slack (plus for just generally building it 🙂 )

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Network Errors and Duplicate Requests in Typesense

Ethan and Rushil were experiencing more than 300 network errors and duplicate requests from Typesense. After rigorous troubleshooting, Jason identified the issue as an Instantsearch-induced multiple re-rendering and implemented a fix. Multiple requests reduced, but networking errors persisted, suggested to be due to client-side internet connectivity.

2mo

Discussing Search API Limitations and Solutions

Sidharth had problems with search API response limitations and sorting issues. Kishore Nallan suggested multi_search query and provided links for an updated version. After installation, some timeout and performance issues were encountered, partially resolved by adjusting client timeout values.

12mo

Production Cluster Failure and Solution

Andrew experienced an unexpected production cluster failure. Kishore Nallan and Jason helped diagnose the problem, remediated it, and upgraded the cluster to prevent future issues.

31mo

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.

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.

30mo