[
https://issues.apache.org/jira/browse/CASSANDRA-16091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189132#comment-17189132
]
Tibor Repasi commented on CASSANDRA-16091:
------------------------------------------
We also have a similar, strange behaviour after upgrading to 3.11.8, with
enabled thrift while having start_rpc disabled in config:
{code}
INFO [main] 2020-09-02 11:59:17,892 YamlConfigurationLoader.java:89 -
Configuration location: file:/etc/cassandra/cassandra.yaml
INFO [main] 2020-09-02 11:59:18,182 Config.java:536 - Node configuration:[...
rpc_address=0.0.0.0; rpc_interface=null; rpc_interface_prefer_ipv6=false;
rpc_keepalive=true; rpc_listen_backlog=50; rpc_max_threads=2147483647;
rpc_min_threads=16; rpc_port=9160; rpc_recv_buff_size_in_bytes=null;
rpc_send_buff_size_in_bytes=null; rpc_server_type=sync;
start_native_transport=true; start_rpc=false; ...
thrift_framed_transport_size_in_mb=15; thrift_max_message_length_in_mb=16;
thrift_prepared_statements_cache_size_mb=null; ...]
...
INFO [main] 2020-09-02 11:59:23,337 StorageService.java:663 - Cassandra
version: 3.11.8
INFO [main] 2020-09-02 11:59:23,337 StorageService.java:664 - Thrift API
version: 20.1.0
INFO [main] 2020-09-02 11:59:23,337 StorageService.java:665 - CQL supported
versions: 3.4.4 (default: 3.4.4)
...
INFO [main] 2020-09-02 11:59:33,491 Server.java:159 - Starting listening for
CQL clients on /0.0.0.0:9042 (unencrypted)...
INFO [main] 2020-09-02 11:59:33,543 ThriftServer.java:116 - Binding thrift
service to /0.0.0.0:9160
INFO [Thread-8] 2020-09-02 11:59:33,549 ThriftServer.java:133 - Listening for
thrift clients...
INFO [main] 2020-09-02 11:59:33,553 CassandraDaemon.java:548 - Not starting
RPC server as requested. Use JMX (StorageService->startRPCServer()) or nodetool
(enablethrift) to start it
{code}
{code}
$ nodetool info
ID : 232f4fe3-051a-4488-97c1-062b733b63e4
Gossip active : true
Thrift active : true
Native Transport active: true
...
{code}
Especially, the last two log entries seem inconsistent.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
