cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9211) Keep history of SSTable metadata
Date Mon, 20 Apr 2015 16:15:59 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-9211:
--------------------------------------
    Reviewer: Marcus Eriksson
    Assignee: Björn Hegerfors

> Keep history of SSTable metadata
> --------------------------------
>
>                 Key: CASSANDRA-9211
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9211
>             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: http://www.datastax.com/wp-content/uploads/2011/10/size-tiered-1.png.
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
(v6.3.4#6332)

Mime
View raw message