[
https://issues.apache.org/jira/browse/CASSANDRA-16091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197197#comment-17197197
]
David Capwell commented on CASSANDRA-16091:
-------------------------------------------
I was able to replicate the original exception with the following
{code}
$ git diff
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index 29442f5387..d815980d56 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -730,7 +730,7 @@ rpc_keepalive: true
#
# Alternatively, can provide your own RPC server by providing the
fully-qualified class name
# of an o.a.c.t.TServerFactory that can create an instance of it.
-rpc_server_type: sync
+rpc_server_type: hsha
# Uncomment rpc_min|max_thread to set request pool size limits.
#
@@ -742,8 +742,8 @@ rpc_server_type: sync
# encouraged to set a maximum that makes sense for you in production, but do
keep in mind that
# rpc_max_threads represents the maximum number of client requests this server
may execute concurrently.
#
-# rpc_min_threads: 16
-# rpc_max_threads: 2048
+rpc_min_threads: 16
+rpc_max_threads: 2048
# uncomment to set socket buffer sizes on rpc connections
# rpc_send_buff_size_in_bytes:
@@ -1057,10 +1057,10 @@ server_encryption_options:
# enable or disable client/server encryption.
client_encryption_options:
- enabled: false
+ enabled: true
# If enabled and optional is set to true encrypted and unencrypted
connections are handled.
optional: false
- keystore: conf/.keystore
+ keystore: ./test/conf/keystore.jks
keystore_password: cassandra
# require_client_auth: false
# Set trustore and truststore_password if require_client_auth is true
{code}
> rpc server gets wrongly initialized with rpc_enabled:false
> ----------------------------------------------------------
>
> Key: CASSANDRA-16091
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16091
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Tom van der Woerdt
> Assignee: David Capwell
> Priority: Normal
> Fix For: 3.11.9
>
>
> After upgrading to Cassandra 3.11.8, Cassandra no longer starts. An exception
> is thrown:
> {code:java}
> java.lang.RuntimeException: Client SSL is not supported for non-blocking
> sockets (hsha). Please remove client ssl from the configuration.
> at
> org.apache.cassandra.thrift.THsHaDisruptorServer$Factory.buildTServer(THsHaDisruptorServer.java:74)
> at
> org.apache.cassandra.thrift.TServerCustomFactory.buildTServer(TServerCustomFactory.java:55)
> at
> org.apache.cassandra.thrift.ThriftServer$ThriftServerThread.<init>(ThriftServer.java:128)
> at org.apache.cassandra.thrift.ThriftServer.start(ThriftServer.java:55)
> at
> org.apache.cassandra.service.CassandraDaemon.startNativeTransport(CassandraDaemon.java:713)
> at
> org.apache.cassandra.service.CassandraDaemon.start(CassandraDaemon.java:538)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:643)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:768)
> {code}
> No configuration changed between 3.11.7 and 3.11.8. rpc_enabled is false in
> both versions.
> I created this Jira issue because clearly something changed between 3.11.7
> and 3.11.8. Maybe intentional, maybe not. Changing `rpc_server_type` (which
> is not clearly documented to be about Thrift only) from `hsha` to `sync` does
> resolve the issue, as expected, but this does seem like a regression, hence
> the Jira issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
