## The problem
Issue typesense/typesense#2208 (closed, 22 comments): Hello, we're trying out the new v28.0 release and are experiencing seemingly random but frequent (like once per hour) crashes of our Typesense pods in AWS EKS. ``` [E112]Not connected to CONTAINER_IP:8107 yet, server_id=8589934875 [R2][E112]Not connected to CONTAINER_IP:8107 yet, server_id=8589934875 [R3][E112]Not connected to CONTAINER_IP:8107 yet, server_id=8589934875 W20250219 08:21:16.843601 190 replicator.cpp:397] Group default_group fail to issue RPC to CONTAINER_IP:8107:8108 _consecutive_error_times=11, [E112]Not connected to 10.10.13.
## What fixed it
[kishorenc (maintainer)]: The fix for ignoring bad DNS resolution is part of the v29.0 GA release. If Typesense pods crash abruptly on EKS with "Not connected" replication errors, upgrade to v29.0.