Configuring a Typesense Cluster
TLDR Chetan had trouble configuring a Typesense cluster and facing issues with "peering-address". Kishore Nallan advised defaults for network settings, understanding Docker's role in networking, and provided tips for troubleshooting. Issue resolved when Chetan used a specific Docker argument.
Aug 23, 2023 (3 months ago)
Chetan
06:05 AM• what should be put in "peering-address"? is it required?
◦ 0.0.0.0 /internal IPs/external IP addresses trigger "failed to listen" errors
◦ leaving it blank starts, but i think typesense sees its own IP in the peers as a different peer with whom it cannot communicate, so it doesn't elect itself leader
• do the instructions for HA assume all the processes are running in the same node? i ask because they all seem to use 192.168-based IPs which are all local to a single machine?
Kishore Nallan
06:12 AM0.0.0.0
-- (default) so I recommend not setting it explicitly.Kishore Nallan
06:12 AMNo, you could have internal IPs that begin with 192.168 for separate machines as well.
Chetan
06:23 AMForce one of the nodes to become a single-node cluster by editing its nodes file to contain just its own IP address
Kishore Nallan
06:24 AMChetan
06:27 AMChetan
06:28 AMKishore Nallan
06:29 AMChetan
06:31 AMKishore Nallan
06:40 AMChetan
03:23 PMKishore Nallan
03:24 PMChetan
03:27 PMChetan
03:28 PMChetan
08:23 PMChetan
10:06 PMAug 24, 2023 (3 months ago)
Chetan
04:27 AMKishore Nallan
04:28 AMKishore Nallan
04:31 AM0.0.0.0
-- it should have internal IPs of the nodes in the cluster.Kishore Nallan
04:33 AM10.
and 172.
getting used so I wonder if there are two networks and Typesense is not picking the correct IP for cluster peering.Kishore Nallan
04:33 AM--peering-address=10.x.x.x
explicitly.Chetan
04:47 AMChetan
04:48 AMKishore Nallan
04:48 AMKishore Nallan
04:49 AMChetan
04:51 AM172.17.0.2:8107
Chetan
04:51 AM--peering-address 172.17.0.2:8107
seems wrong?Chetan
04:52 AMKishore Nallan
04:52 AMKishore Nallan
04:53 AMChetan
04:58 AMChetan
04:58 AMChetan
04:59 AM--network host
argument (not the most security-ideal solution, but works for this case)Kishore Nallan
05:01 AMTypesense
Indexed 3011 threads (79% resolved)
Similar Threads
Troubleshooting Multi-Node Setup in Docker
Harpreet experienced issues running a multi-node setup on Docker and received troubleshooting advice and alternative solution from Kishore Nallan.
Setting Up HA Cluster on Fly with Typesense
Jordan needed help setting up an HA cluster on Fly for Typesense. Jason assisted in troubleshooting the configuration and 6tunnel usage. Eventually, a solution was found in the Fly community forum.
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.
Testing High Availability with Raft Returns Crashes
pboros reports an issue with usual crashes when testing high availability with Raft. Kishore Nallan suggests checking the quorum recovery period and efficiently logging the crash on all nodes. The issue persists, with pboros suspecting it's due to hostname being no longer resolvable once a container is killed.
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.