[
https://issues.apache.org/jira/browse/CASSGO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18051768#comment-18051768
]
João Reis commented on CASSGO-72:
---------------------------------
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)
> Add support for aws keyspaces peering
> -------------------------------------
>
> Key: CASSGO-72
> URL: https://issues.apache.org/jira/browse/CASSGO-72
> Project: Apache Cassandra Go driver
> Issue Type: Improvement
> Components: Core
> Reporter: João Reis
> Priority: Normal
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> AWS Keyspaces with peering enabled returns 127.0.0.1 on system.local and then
> returns the same host id in system.peers with the valid IP address. The
> driver needs to ignore the local host in this scenario.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
