[
https://issues.apache.org/jira/browse/CASSANDRA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779119#comment-13779119
]
Jonathan Ellis commented on CASSANDRA-5515:
-------------------------------------------
- Could we put the clearSSTableReadMeter in CFS or SSTR? Or put it in
SSTableDeletingDask instead of making it a notification at all. Alternatively,
since it's just one row I'd lean towards just letting TTL take care of it.
- Does TTL need to be so long if we're persisting every 5m?
- It looks like having the increments in the read section of the iterators
means we only increment in index lookup ({{getPosition}}) is successful. IMO
we should increment before getPosition. May be cleaner to do this in
collationController but iterator constructor also works.
- Use Keyspace.SYSTEM_KS instead of hardcoding {{"system"}}
- What can we do to restore coldness data from a snapshot?
> Track sstable coldness
> ----------------------
>
> Key: CASSANDRA-5515
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5515
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Tyler Hobbs
> Fix For: 2.0.2
>
> Attachments: 0001-Track-row-read-counts-in-SSTR.patch, 5515-2.0-v1.txt
>
>
> Keeping a count of reads per-sstable would allow STCS to automatically ignore
> cold data rather than recompacting it constantly with hot data, dramatically
> reducing compaction load for typical time series applications and others with
> time-correlated access patterns. We would not need a separate age-tiered
> compaction strategy.
> (This will really be useful in conjunction with CASSANDRA-5514.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
