[
https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762995#comment-17762995
]
Ahmed ELJAMI commented on CASSANDRA-16999:
------------------------------------------
Hi,
_Cassandra version: 4.0.5_
_Java Driver Version: 3.11.4_
We are trying to enable SSL between the client and Cassandra cluster but we
encountered the same issue as described here.
With a cluster of 2 nodes (The client uses these 2 nodes as contact_points), we
saw that the driver tried to connect to the second node using the port 9042:
{code:java}
10:26:31.474 [cluster1-nio-worker-0] WARN c.d.driver.core.HostConnectionPool -
Error creating connection to X.X.X.X/X.X.X.X:9042
com.datastax.driver.core.exceptions.TransportException: [X.X.X.X/X.X.X.X:9042]
Channel has been closed
10:26:31.475 [cluster1-nio-worker-0] WARN com.datastax.driver.core.Session -
Error creating pool to X.X.X.X/X.X.X.X:9042
com.datastax.driver.core.exceptions.ConnectionException: [X.X.X.X/X.X.X.X:9042]
Pool was closed during initialization{code}
Do you think that the fix will also be applied for 4.0.X ?
Thanks :)
> system.peers and system.peers_v2 do not contain the native_transport and/or
> native_transport_port_ssl
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16999
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16999
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
> Reporter: Steve Lacerda
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> system.peers_v2 includes a “native_port” but has no notion of
> native_transport_port vs. native_transport_port_ssl. Given this limited
> information, there’s no clear way for the driver to know that different ports
> are being used for SSL vs. non-SSL or which of those two ports is identified
> by “native_port”.
>
> The issue we ran into is that the java driver, since it has no notion of the
> transport port SSL, the driver was only using the contact points and was not
> load balancing.
>
> The customer had both set:
> native_transport_port: 9042
> native_transport_port_ssl: 9142
>
> They were attempting to connect to 9142, but that was failing. They could
> only use 9042, and so their applications load balancing was failing. We found
> that any node that was a contact point was connecting, but the other nodes
> were never acting as coordinators.
>
> There are still issues in the driver, for which I have created JAVA-2967,
> which also refers to JAVA-2638, but the system.peers and system.peers_v2
> tables should both contain native_transport_port and
> native_transport_port_ssl.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
