[
https://issues.apache.org/jira/browse/CASSANDRA-14904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814423#comment-16814423
]
Jan Karlsson commented on CASSANDRA-14904:
------------------------------------------
I scraped together some time to have a look. LGTM for the most part, but I have
some thoughts.
I have been thinking of the use case where both native_transport_port and the
native_transport_port_ssl are set.
1. With this patch, the behavior will be that we will always use the
native_transport_port_ssl if both are set unless overridden by command line. I
don't necessarily see a problem with that but it might not be very transparent
behavior.
2. No matter what we choose to do about this behavior, a test case that tests
the case of both being set would be good to add.
> SSTableloader doesn't understand listening for CQL connections on multiple
> ports
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-14904
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14904
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Kurt Greaves
> Assignee: Ian Cleasby
> Priority: Low
> Fix For: 4.0, 3.11.x
>
>
> sstableloader only searches the yaml for native_transport_port, so if
> native_transport_port_ssl is set and encryption is enabled sstableloader will
> fail to connect as it will use the non-SSL port for the connection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
