Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
Hi,
If one has a large number of keyspaces, I assume this may result in many SStables, which may be the reason why the time it takes quite a while for Cassandra to start.
Correct me if I'm wrong, but it appears that Cassandra goes over every SStable and reads its metadata so that the reason may be the large proportion of files.
Is there a way to set old keyspace as archived keyspaces that are only loaded lazily?
The number of keyspaces is related to the long startup but ultimately the number of tables is the biggest contributor to the duration of Cassandra's startup sequence.
If you inspect the system.log closely, you will likely see that most of the time is spent between these 2 log entries:
INFO [main] 2020-07-31 00:51:15,555 Gossiper.java:1723 - No gossip backlog; proceeding INFO [main] 2020-07-31 00:54:06,867 NativeTransportService.java:70 - Netty using native Epoll event loop
These entries were taken from a node running Cassandra 3.11.3.
Between waiting for gossip to settle (message from Gossiper.java class above) and the native transport service initialising (message from NativeTransportService.java), the classes CompactionStrategyManager and DiskBoundaryManager are doing most of the work during the initialisation process.
You can see this for yourself if you go through the debug.log. In fact, you will see repeated message entries indicating that C* is updating the disk boundaries. You can conclude from this that the length of time it takes for C* to initialise is proportional to the total number of tables in the cluster (regardless of how many keyspaces there are).
The CassandraDaemon.setup() method deals with initialising Cassandra. This section of the code (in C* 3.11.3) are the steps I refer to above if you're interested in the details of the startup sequence.
To answer your other question, there isn't a way of selecting which keyspaces/tables get loaded on startup. Cassandra needs to pre-load the data on disk so it knows what it owns. Cheers!
5 People are following this question.
