Troubleshooting Multi-node Kubernetes Clustering Issue
TLDR Vasudev faced an issue in Kubernetes clustering. Kishore Nallan suggested updating the nodes file to single pod configuration, which would allow the remaining pod to recover automatically.
Mar 14, 2023 (9 months ago)
Vasudev
03:19 AM
Kishore Nallan
03:22 AMKishore Nallan
03:22 AMVasudev
03:23 AMKishore Nallan
03:29 AMVasudev
03:46 AMMulti-node with no leader: refusing to reset peers.Kishore Nallan
03:50 AMKishore Nallan
03:50 AM
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting IP Update on Kubernetes Typesense
Alessandro and Damien are having issues with old IP addresses in a Kubernetes Typesense cluster not being updated. Kishore Nallan provides possible troubleshooting solutions, and mentioned the need for a fix for DNS retries. A suggested update strategy was shared by Aljosa.
Solutions for HA Issues Running Typesense in Kubernetes
Lane shared a solution for fixing HA issues in k8s, involving an InitContainer to update the config map. Kishore Nallan introduced a cluster auto reset peers feature. Users discussed limitations in the approach and potential deployment considerations.
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.
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.
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.