Tibor Repasi created CASSANDRA-14811:
----------------------------------------
Summary: RPC_READY flag handled inconsistently
Key: CASSANDRA-14811
URL: https://issues.apache.org/jira/browse/CASSANDRA-14811
Project: Cassandra
Issue Type: Bug
Components: Distributed Metadata
Reporter: Tibor Repasi
With version 3.0.17 we experience an inconsistent handling of the RPC_READY
flag. We identified 3 scenarios with an unexpected behaviour.
# Using {{nodetool disablebinary}} on a node in normal operation
** Observed behaviour:
*** (/) the CQL listener is closed and Netty shut down
*** (x) gossipinfo still contain the {{RPC_READY}} *true* advertisement.
** Expected behaviour: gossip announcement of the {{RPC_READY}} flag should
switch to *false.* This is what we observe with version 2.2.13
# Starting up a node with JVM option
{{-Dcassandra.start_native_transport=false}}
** Observed behaviour:
*** (/) Netty is not started to listen for CQL clients
*** (/) logging {{cassandra[1765]: INFO 13:58:46 Not starting native transport
as requested. Use JMX (StorageService->startNativeTransport()) or nodetool
(enablebinary) to start it}}
*** (?) the gossipinfo does not contain the {{RPC_READY}} flag at all,
however, this is also observed on 2.2.13.
# Issuing {{nodetool enablebinary}} command on a node started with
{{-Dcassandra.start_native_transport=false}}
** Observed behaviour:
*** (/) Netty is started up and open the CQL port for listening
*** (x) the {{RPC_READY}} flag is not announced for this node any more,
causing clients to not consider this note up and not trying to connect.
** Expected behaviour: gossip flag {{RPC_READY}} should be added to announce
*true*, as observed with version 2.2.13.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
