Adriaan
06/10/2025, 9:05 AMW20250610 06:48:09.540362 266 node.cpp:1559] node default_group:10.52.1.20:8107:8108 request PreVote from 10.52.19.10:8107:8108 error: [E110]Fail to connect Socket{id=764504179018 addr=10.52.19.10:8107} (0x0x7f9bfc004c00): Connection timed out
W20250610 06:48:09.540470 276 node.cpp:1559] node default_group:10.52.1.20:8107:8108 request PreVote from 10.52.2.30:8107:8108 error: [E110]Fail to connect Socket{id=755914244417 addr=10.52.2.30:8107} (0x0x7f9bfc003580): Connection timed out
I20250610 06:48:11.241796 214 raft_server.cpp:683] Term: 11, pending_queue: 0, last_index: 1822148, committed: 0, known_applied: 1821784, applying: 0, pending_writes: 0, queued_writes: 0, local_sequence: 37509018
Also, after restarting the last node, he still tries to connect to the old nodes. So this is cached somewhere. Why is this happening and how can I clear this cache?Alan Martini
06/10/2025, 4:16 PMexec into the running container and cat the file? Make sure the content matches what you expect.
- If you're parsing and generating this file dynamically, ensure there is no delay or race condition between the Kubernetes state change and the file update inside the container.
Typesense doesn’t cache peer IPs across restarts or hold onto IPs that are no longer present in the nodelist file. If it’s still trying to connect to stale IPs, either:
1. The file hasn’t been updated properly inside the container
2. Or, it is being overwritten back to the older list by something like an init container or lifecycle hookKyriakos Akriotis
06/10/2025, 5:47 PMAdriaan
06/11/2025, 9:44 AM