[
https://issues.apache.org/jira/browse/CASSANDRA-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537511#comment-17537511
]
Brandon Williams commented on CASSANDRA-17602:
----------------------------------------------
It adds another encrypted storage on ssl_storage_port, since nodes before 4.0
won't know about the storage port handling encrypted traffic. So I think I was
wrong and we don't need -ssp, and can just point -sp at whatever port is bound
and we can negotiate it, but the devil is always in the details when you get to
implementation.
> sstableloader not respecting conf-path flag
> -------------------------------------------
>
> Key: CASSANDRA-17602
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17602
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
> Reporter: Aswin Karthik
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1-beta
>
>
> Hello,
> sstableloader does not seem to respect the config file flag (-f) and the
> storage port flag.
>
> We run our cluster on a different storage port with encryption. We construct
> a YAML with {{server_encryption_options}} and {{client_encryption_options}}
> and pass the storage port flag (both {{-sp}} and {{-ssp}}).
>
> However, we noticed that both the storage port flag and encryption settings
> are getting picked from the default config file {{conf/cassandra.yaml}} and
> ends up connecting to 7000 port unencrypted. As a workaround, we have added
> the storage port configuration to the YAML and copy our configuration file
> and overwrite the {{conf/cassandra.yaml}} and it is working now.
>
> Also to be noted that using the {{-f}} works in Cassandra 3.x. The bug seems
> to be present in 4.x versions only.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
