Hallo everyone,
I’ve just started off testing Cassandra 5.0 for production purposes and I’ve
found an “interesting” change: during bootstrap (joining or replacing a dead
node), it seems nodetool cannot reach the server until the bootstrap has
completed:
Mar 14 15:57:16 *** cassandra[65339]: INFO [main] 2025-03-14 15:57:16,211
RangeStreamer.java:358 - Bootstrap: range
Full(/***:7000,(-5336381718024909890,-5311714841097861693]) exists on
Full(/***:7000,(-5336381718024909890,-5311714841097861693]) for keyspace test2
Mar 14 15:57:16 *** cassandra[65339]: INFO [main] 2025-03-14 15:57:16,211
RangeStreamer.java:358 - Bootstrap: range
Full(***:7000,(5618289732966892333,5629519774009004161]) exists on
Full(***:7000,(5618289732966892333,5629519774009004161]) for keyspace test2
^C
***:/var/lib/cassandra$ nodetool netstats
Exception in thread "main" java.lang.IllegalArgumentException: Server is not
initialized yet, cannot run nodetool.
at org.apache.cassandra.tools.NodeTool.err(NodeTool.java:320)
at org.apache.cassandra.tools.NodeTool.execute(NodeTool.java:283)
at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:85)
As the log stated the node is already streaming, nodetool says the server is
not initialized yet. Finally, the node was bootstrapped correctly and enabled
the nodetool access when it jumped to normal. In production operations we were
used to monitor the bootstrap process using nodetool netstats, which now seems
not available anymore. The question now is whether this is a bug or do we have
another way to monitor the process?
Best regards,
Tibor Répási
