cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bin Chen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-11708) sstableloader not work with ssl options
Date Wed, 04 May 2016 04:02:13 GMT
Bin Chen created CASSANDRA-11708:
------------------------------------

             Summary: sstableloader not work with ssl options
                 Key: CASSANDRA-11708
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11708
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
            Reporter: Bin Chen
            Priority: Minor


My cassandra server start with client_encryption_options.
{code}
client_encryption_options:
    enabled: true
    keystore: /path/to/keystore.node0
    keystore_password: cassandra
    require_client_auth: true
    truststore: /path/to/truststore.node0
    truststore_password: cassandra
{code}
when I use sstableloader with -ts/-tspw/-ks/-kspw, I get
{code}
All host(s) tried for query failed (tried: localhost/127.0.0.1:9042 (com.datastax.driver.core.TransportException:
[localhost/127.0.0.1:9042] Channel has been closed))
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query
failed (tried: localhost/127.0.0.1:9042 (com.datastax.driver.core.TransportException: [localhost/127.0.0.1:9042]
Channel has been closed))
{code}

after looked at the code, I found only one way to active ssl is use -f with a configuration
yaml file which has 
{code}
client_encryption_options:
    enabled: true
{code}

so I think it's a bug, better to active ssl when I set -ts and -tspw.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message