cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert P Tobey (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9517) Switch to DTCS for hint storage
Date Fri, 29 May 2015 21:42:17 GMT


Albert P Tobey commented on CASSANDRA-9517:

My original theory was that we could use DTCS for system.hints since it has a timeseries-like
table definition and let it delete whole tables when the TTLs expire. That was before I understood
exactly how tombstones are used in hints. The patch seemed to help a little in testing, but
I did not figure out why it seemed that way.

The forced major compaction is most of the problem when hints build up, so that's the thing
that needs to be removed if at all possible. Under 100% write workload on very fast machines
I was seeing system.hints compactions in excess of 100GB, which has all kinds of negative

If there's a way we can convince any of the compaction strategies to split the wide rows across
sstables (split by time window) while only merging tombstones along with subsequent cleanup,
that could make hints tolerable until 3.0 takes over the world.

> Switch to DTCS for hint storage
> -------------------------------
>                 Key: CASSANDRA-9517
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>             Fix For: 2.1.6
> The DateTieredCompactionStrategy is a good choice for HintedHandoff so that we reduce
the compaction load we incur when users build up hints.  [] and others
have tried the following patch in various setups and have seen significantly less load from
hint compaction.
> Setting the time window to 10 minutes has shown additional improvement.
> [~krummas] do you have any feedback about this idea and/or settings?

This message was sent by Atlassian JIRA

View raw message