[
https://issues.apache.org/jira/browse/CASSANDRA-14291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416270#comment-17416270
]
Stefan Miklosovic commented on CASSANDRA-14291:
-----------------------------------------------
This should be possible to do completely offline as I just scanned the code
fastly but we might need to reshuffle things a little bit here and there. I
agree with having this done in a purely offline fashion. I would not merge this
with "upgradesstables", upgrading is upgrading ... not rewriting imho, plus I
do not think renaming that existing nodetool command is a good idea either,
people are used to that one already and that renaming would be quite
disruptive. I am not sure what is the policy here about nodetool renaming, I
have never encountered that problem before.
> Nodetool command to recreate SSTable components
> -----------------------------------------------
>
> Key: CASSANDRA-14291
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14291
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Kurt Greaves
> Assignee: Alexander Ivakov
> Priority: Low
> Labels: 4.0-feature-freeze-review-requested
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
