[CASSANDRA-17602] sstableloader not respecting conf-path flag

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0.5, 4.1-beta1, 5.0-alpha1, 5.0
• Component/s: Tool/bulk load
• Platform: All
• Since Version: 4.0.0

Source Control Link

https://github.com/apache/cassandra/commit/2531dd1ebaeab4e71f970e27a5dd962ceb6b790b

Test and Documentation Plan

fixed unit tests

• Assignee: Stefan Miklosovic
• Reporter: Aswin Karthik

Authors

Stefan Miklosovic

Reviewers

Brandon Williams, Jon Meredith, Stefan Miklosovic

• Created: 05/May/22 12:54
• Updated: 12/Sep/23 13:02
• Resolved: 16/Jun/22 17:49

Description

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.