Troubles in Synchronising 2 Machine Cluster
TLDR Janne had trouble with a 2 machine cluster synchronisation, Kishore Nallan informed a minimum of 3 nodes are required for quorum.
Oct 12, 2021 (25 months ago)
Janne
12:51 PMW20211012 12:47:32.217510 27509 node.cpp:2308] node default_group:10.6.5.21:8107:8108 reject term_unmatched AppendEntries from 10.6.5.20:8107:8108 in term 20 prev_log_index 20 prev_log_term 5 local_prev_log_term 3 last_log_index 16195 entries_size 0 from_append_entries_cache: 0
Any idea what causes this?
Kishore Nallan
12:53 PMJanne
12:53 PM
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
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.
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.
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.