Resolving Data Discrepancy in Cluster Upload
TLDR Nelson raised a concern about a possible discrepancy in document counts amongst nodes after a data cluster upload, with an issue on node 1. Jason queried if node 1's count was still stagnant.
Oct 13, 2021 (27 months ago)
Nelson
04:50 AMnode 1, 2,3.
There is a way to execute a command that replicates the differences in the number of documents? Remember that node 1 stopped for some reason as the data is upload.
Jason
05:19 AM
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Docker Nodes - Memory and Data Insertion Inconsistencies in Cluster
Nelson experienced issues with Docker in a 3-node cluster. After recovering node 1, they noticed different memory use and data insertion rates. Jason clarified that these differences occur due to the index rebuilding process.
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.
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.