joao-r-reis commented on issue #1873: URL: https://github.com/apache/cassandra-gocql-driver/issues/1873#issuecomment-3749105049
Good to know the issue is fixed. Copy pasting my JIRA comment here for future reference: > This issue is fixed in 2.0.0, adding some context here for future reference: > > GoCQL 1.x used the connection address instead of system.local during session startup but whenever a topology refresh happened (triggered by a topology event or control connection reconnection) the refresh operation took the IP address from system.local and replaced the connection address of the initial control host with the system local address. This inconsistency is not ideal so in 2.0.0-rc1 we initially resolved the inconsistency by always taking the system.local address even at startup. Unfortunately this broke some use cases like single cluster deployments using docker if the proper broadcast_address value wasn't set in the configuration. > > In 2.0.0 we implemented a change that essentially resolves the 1.x inconsistency issue in the opposite direction, i.e., by always preserving the connection address and always ignoring the system.local address. This last change is what fixed the aws keyspaces issue. > > There's been some talks about improving this because ignoring system.local also has its issues (see https://issues.apache.org/jira/browse/CASSGO-96) > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
