[
https://issues.apache.org/jira/browse/CASSANDRA-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542657#comment-17542657
]
Stefan Miklosovic commented on CASSANDRA-17602:
-----------------------------------------------
I debugged it more when it comes to the test issues we were discussing here (1).
I added printing of tool.getStdout() and tool.getStderr() into that test to see
what it contains.
stdout
||Exception||IDEA||Jenkins logs||
|SSLHandshakeException|no|yes|
|TransportException|yes|yes|
stderr
||Exception||IDEA||Jenkins logs||
|SSLHandshakeException|no|no|
|TransportException|yes|yes|
Right now, the current upstream code checks SSLHandshakeException on stdout.
This makes the test passing in Jenkins but not in IDEA. The common case for
both environment is TransportException in either stdout or stderr. I would
change it to check TransportException in stdout (currently the check is done on
stdout too).
Honestly, I do not have any idea where this difference comes from.
(1) [https://github.com/apache/cassandra/pull/1632#discussion_r876199710]
> 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
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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]
