Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Duplicate
-
None
-
Availability - Unavailable
-
Normal
-
Normal
-
User Report
-
All
-
None
-
Description
After upgrading to Cassandra 3.11.8, Cassandra no longer starts. An exception is thrown:
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)
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.
Attachments
Issue Links
- is duplicated by
-
CASSANDRA-16127 NullPointerException when calling nodetool enablethrift
- Resolved