Node 1 Resetting Issue & Document Update Problem
TLDR Nelson experienced issues after resetting node 1. Kishore Nallan suggested halting Typesense, erasing data directory, and restarting Typesense to resolve issue.
1
Oct 13, 2021 (25 months ago)
Nelson
05:57 AM
Kishore Nallan
07:27 AMAlso, can you please post follow up questions to this convo in this same thread? Will help us manage the messages on the Slack channel better. :ty:
1
Oct 14, 2021 (25 months ago)
Nelson
01:02 AM
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
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.
Resolving Error in Node Restore
Nelson encountered error restoring node 2. Jason provided advice on correct node data handling. Nelson resolved the problem by deleting unnecessary data and re-running the node. Kishore Nallan affirmed this solution.
Troubleshooting 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.