Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
None
-
Operability
-
Low Hanging Fruit
-
All
-
None
-
Description
We've had a situation where our backup-restore flow did not include summary.db component for a large file with a lot of keys. This caused Cassandra on the restored node to take a long time to boot (while it was building the summary).
The last message was about opening a few sstables. It would be nice to also include a debug line about building summary, which then operators can use to check if a missing summary file is expected.