Resolving Unhealthy Typesense Cluster and JSON Parsing Bug
TLDR 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.





Apr 23, 2021 (29 months ago)
Masahiro
01:33 AMAny ways to fix this issue? If there are documentations about this, it will be helpful 😄
Jason
01:33 AMMasahiro
01:34 AMJason
01:39 AMMasahiro
01:40 AM{
'name': 'users',
'fields': [
{'name': 'displayName', 'type': 'string' },
{'name': 'userId', 'type': 'string' },
{'name': 'favGameTitle1','optional':'true', 'type': 'string' },
{'name': 'gender', 'optional':'true', 'type': 'int32' },
],
'default_sorting_field': 'gender'
}
Masahiro
01:41 AMJason
01:42 AMWe currently expect
optional
to have values of true
or false
. Looks like a string value of "true"
for optional crashes the server 😞Jason
01:44 AMtrue
and false
in the schema?Masahiro
01:44 AMMasahiro
01:44 AMJason
01:45 AM
Jason
01:45 AM
Jason
01:48 AMCould you confirm that you're ok with this Masahiro
Masahiro
01:50 AMJason
01:50 AMJason
01:50 AMJason
01:51 AMMasahiro
01:51 AMJason
01:52 AMJason
01:54 AMMasahiro
01:57 AMJason
01:59 AM

Apr 29, 2021 (29 months ago)
Jason
07:08 AM
Masahiro
07:12 AMMasahiro
07:14 AMJason
07:59 AM

Typesense
Indexed 2764 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.
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.


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.


Troubleshooting Typesense Cluster Multi-node Leadership Error
Bill experienced a problem with a new typesense cluster, receiving an error about no leader and health status issues. Jason and Kishore Nallan provided troubleshooting steps and determined it was likely due to a communication issue between nodes. Kishore Nallan identified a potential solution involving resetting the data directory. Following this, Bill reported the error resolved.
Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.


