This is possibly related to 20.6.1 from 5.0.9 .NET client .
I’m trying to connect a client using the older 5.0.9 TCP client to a new 20.10 cluster. Tls can be off (they’re all within a private VNET). If I specify the IP of the leader, then connection/queries work fine. If I try specifying all the IPs in a gossip connection string, I get an exception saying the connection was closed.
My gossip results seem fine (to me)… (hitting …:2113/gossip?format=json ).
One thing that may or may not be related is that I cannot set the ExtIp in the yaml file to the IP address of the VM. If I try to set ExtIp I get the exception :
[ 3860,11,21:27:29.464,INF] ========== [“18.104.22.168:2113”] SYSTEM INIT…
[ 3860, 1,21:27:29.483,FTL] Unable to start Kestrel.
System.Net.Sockets.SocketException (10049): The requested address is not valid in its context.
Although if I set it as 0.0.0.0 then it starts and I’m able to hit the leader without issue.
Any suggestions/tips will be highly appreciated. Yes, we’ll be moving to gRPC eventually but want to try and “drop in replace” 20.10 without having to tinker with clients first.