[
https://issues.apache.org/jira/browse/CASSANDRA-15755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Joshi updated CASSANDRA-15755:
-------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Status: Open (was: Triage Needed)
> Add a debug line informing of building summary during sstable open
> ------------------------------------------------------------------
>
> Key: CASSANDRA-15755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15755
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Logging
> Reporter: Sumanth Pasupuleti
> Assignee: Sumanth Pasupuleti
> Priority: Low
> Fix For: 4.x
>
> Attachments: 15755-4.0.txt
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
