[ 
https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813052#comment-17813052
 ] 

Bret McGuire commented on CASSANDRA-16999:
------------------------------------------

Okay, so here's where things stand as of this writing.

 

I've re-opened JAVA-2967 (where the original work was done to support this 
functionality for DSE 6.8 for the 3.x Java driver).  That ticket will be used 
to govern the inclusion of similar functionality for OSS C* (since it already 
comes loaded with all the context).  I've added a 
[PR|https://github.com/apache/cassandra-java-driver/pull/1911] for the 3.x Java 
driver which should add support for the OSS C* columns.

 

I've also filed a new ticket (CASSANDRA-19352) aimed at bringing this 
functionality to the 4.x Java driver.

> 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: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to