cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Ivakov (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-14291) Nodetool command to recreate SSTable components
Date Thu, 12 Jul 2018 05:50:00 GMT


Alexander Ivakov updated CASSANDRA-14291:
    Status: Patch Available  (was: Open)


Added nodetool command recreatesstablecomponents
Takes keyspace and table arguments.
Flags to set which component(s) to re-create.
Re-creating the primary-index, compression info, secondary index, stats triggers upgradesstables
and all components are re-written (including the data).
Re-creating bloom-filter, summary or table-of-contents (TOC) done separately and faster (not
re-writing the data).
Added a function to re-write TOC.
Added test for rebuilding summary, rebuilding bloom filter and re-writing TOC.

> Nodetool command to recreate SSTable components
> -----------------------------------------------
>                 Key: CASSANDRA-14291
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Kurt Greaves
>            Assignee: Alexander Ivakov
>            Priority: Minor
> Need a JMX/Nodetool command to recreate components for SSTables without re-writing the
data files.
> Possible implementation idea:
> Create a {{nodetool (recreate|regen)component}} command that would enable you to recreate
 specific components of an SSTable, and also allow specifying SSTables or columnfamilies.
> I'd say a flag for a list of components and a flag for SSTables with keyspace.columnfamilies
as positional arguments would work
> Alternatively this could become part of upgradesstables, but would likely make that command
a bit bloated.
> Background:
> In CASSANDRA-11163 we changed it so summaries and bloomfilters were not regenerated or
persisted on startup. This means we would rely on compactions/upgrades to regenerate the bloomfilter
(or other components) after a configuration change. While this works, it's pretty inefficient
on large tables just because you changed the bloomfilter size or summary chunk sizes.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message