Cassandra keyspaces created with new storage strategy should not use date-tiered compaction
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Eevans
	Oct 23 2017, 9:59 PM

Description

Cassandra keyspaces in the new storage strategy (i.e. storage of current-and-recent) continue to be setup to use the date-tiered compaction strategy, and should use size-tiered instead.

Related Objects

Mentioned In: T179105: Change new storage strategy defaults for Cassandra compression
Mentioned Here: T179083: Cassandra schema creation seems unreliable

Event Timeline

Eevans created this task.Oct 23 2017, 9:59 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 23 2017, 9:59 PM

Eevans triaged this task as Medium priority.Oct 23 2017, 10:00 PM

Eevans added projects: User-Eevans, RESTBase-Cassandra.Oct 27 2017, 2:29 PM

Eevans moved this task from Backlog to Next on the User-Eevans board.Nov 20 2017, 5:12 PM

This will require an increment of the schema version, and will kick off schema migration in the production cluster the first time it is deployed. This seems worth avoiding if possible.

Eevans moved this task from Next to Blocked on the User-Eevans board.Nov 20 2017, 8:42 PM

• mobrovac added a project: Platform Team Legacy (Later).Dec 20 2018, 12:16 PM

This issue is no longer relevant; Closing

Cassandra keyspaces created with new storage strategy should not use date-tiered compactionClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Cassandra keyspaces created with new storage strategy should not use date-tiered compaction
Closed, ResolvedPublic
Actions