Steve Lacerda created CASSANDRA-16999:
-----------------------------------------
Summary: 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
Reporter: Steve Lacerda
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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
