cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-9211) Keep history of SSTable metadata
Date Thu, 18 Feb 2016 13:30:18 GMT


Marcus Eriksson resolved CASSANDRA-9211.
    Resolution: Duplicate

Closing this as a duplicate - CASSANDRA-10805 is probably a better way to store information
to visualize compactions

> Keep history of SSTable metadata
> --------------------------------
>                 Key: CASSANDRA-9211
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Björn Hegerfors
>            Assignee: Björn Hegerfors
>            Priority: Minor
> Similar to the request in CASSANDRA-8078, I'm interested in SSTables' lineage. Specifically,
I want to visualize the behaviors of compaction strategies based on real data. For example,
for STCS I might want to generate something like this image:
For LCS and DTCS, other properties than size are interesting.
> As Marcus responded in CASSANDRA-8078, there is already tracking of ancestors in the
SSTable metadata. But as far as I know, the metadata gets garbage collected along with the
SSTable itself. So what I propose is to persist metadata in a system table. Maybe some, maybe
all metadata. Like the compaction_history table, this should have a default TTL of something
like one week or just one day. But users can freely modify/remove the TTL.

This message was sent by Atlassian JIRA

View raw message