Issues with API Key and Cluster Updates in Typesense
TLDR Jordan was having issues with API key and cluster updates. Jason explained the problem could be due to a split brain situation and suggested a solution. Sai also reported facing the same issue.
Sep 12, 2023 (2 months ago)
Forbidden - a valid x-typesense-api-key header must be sent.
What’s odd is that the id returned from the
/keysquery is 0…could this mean that the key is not saved across all nodes in my cluster and the leader finally changed?
Indexed 3015 threads (79% resolved)
Converting Single Node to Cluster and Problem-Solving
Albert requested help for enjoying a single node to a cluster, checking health, and handling API keys. Jason clarified API keys, identified and explained the issue of having "no leader", and provided methods to fix it.
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.
Debugging and Recovery of a Stuck Typesense Cluster
Charlie had a wedged staging cluster. Jason provided debugging and recovery steps, and Adrian helped with more insights. It turns out the issue was insufficient disk space. Once Adrian increased the disk size, the cluster healed itself.
Debugging Typesense API Key Error
James is getting an error related to the `x-typesense-api-key` header in their Typesense project. Harrison suggests passing the API key in the HTTP header, and Jason advises checking the key via curl and possibly closing a duplicate Typesense server.
Trouble with Typesense Cloud HA document updates
Tariq reported duplicate document creation issue in Typesense during rapid write and read operations. Jason suggested reading from the node leader. Tariq resolved the issue by caching IDs of newly created documents.