Troubleshooting Unhealthy Typesense Server and Schema Issues
TLDR Akash was having consternation over an unhealthy Typesense server and malaffected schema. Kishore Nallan suggested a probable resource deficiency and asked for more details via a DM.
1Dec 31, 2022 (9 months ago)
Akash
08:15 AM1
Kishore Nallan
08:15 AM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Resolving Unhealthy Typesense Cluster and JSON Parsing Bug
Masahiro reported an unhealthy Typesense cluster. The cause was a parsing bug related to boolean values in JSON schemas. Jason resolved the issue by clearing node data and upgrading the server to v0.20, which resolved the issue and Masahiro's team decided to use Typesense.
7Troubleshooting Typesense Cluster Mode Error Logs
gaurav was having troubles with Typesense error logs in cluster mode. Kishore Nallan explained that it can occur due to master's location troubles and node restarts or state resets, especially in a 3-node setup.
Discussion About Typesense Nodes Not Synchronizing Correctly
Erick experienced an issue where documents weren't updated properly in a Typesense instance running on 3 nodes. Upon requesting debug logs and configs, Jason identified that these nodes weren't part of the same cluster. They couldn't resolve the nodes' failure to connect issue and recommended a fresh installation.
2