Neither of those changes should have had any effect on client connections, as they only relate to internode communication. Your go client should have specified the public ip addresses as per the broadcast RPC address, and would need to be specifying the live node as the connection point to work. I suspect you encountered a situation where the addresses specified in your go client were the decommissioned nodes and maybe it didn't attempt all nodes or the live node was initially missing from that list?
raft.so - Cassandra consulting, support, and managed services On Thu, May 6, 2021 at 11:35 PM MyWorld <timeplus.1...@gmail.com> wrote: > Hi All, > > We had a set up of 3 node single DC cluster on Google cloud with RF=3 for > development purposes. Service Team hosted in Dallas servers was able to > connect from php as well as golang code properly. Initially we have set up > the following settings in cassandra.yaml: > Listen address: <Private IP> > Broadcast address: <Private IP> > Seeds: <PrivateIP> > Rpc address: 0.0.0.0 > Broadcast rpc address: <Public IP> > > Due to cost factor, we removed 2 nodes from our DC and now we had a single > node DC cluster with RF=1 (therefore no peers). > > After rebooting the servers(in Dallas) at service end, php code was able > to connect properly. But from go lang service, we started getting the > following error: "no connections were made when creating the session". We > firstly set DisableInitialHostLookup to true,but that didn't resolve the > issue. When we make below changes in cassandra.yaml ,this issue was > resolved: > Broadcast address: <Public IP> > Seeds: <Public IP> > > Now, not able to understand: > 1. Why was there no issue when we had 3 node DC set up with the broadcast > address set to PrivateIP? > 2. How does change in Broadcast address from private to public has an > impact on client connection for single node DC since we already had rpc > broadcast address set to public for remote clients. > > Please help me understand this. > > Regards, > Ashish Gupta >
