[
https://issues.apache.org/jira/browse/CASSANDRA-14197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406068#comment-16406068
]
Marcus Eriksson commented on CASSANDRA-14197:
---------------------------------------------
pushed a new version here:
https://github.com/krummas/cassandra/commits/marcuse/autoupgrade-v2
Idea is that if there is no other compaction to do for a table, we will pick
the oldest non-upgraded sstable and upgrade it. The patch also adds
old-sstable-count to {{nodetool tablestats}} and a metric so that users can
know when they are fully upgraded. There will be no starvation of tables that
we don't write anything to since we have
[this|https://github.com/krummas/cassandra/blob/marcuse/autoupgrade-v2/src/java/org/apache/cassandra/service/CassandraDaemon.java#L408]
which checks if there are compactions to do every minute. Only time we won't
run an upgrade for a long time is if we are way behind on compactions, and in
this case it is probably better to just let standard compactions run the
upgrades until we catch up. Users can either enable this feature in
cassandra.yaml or via JMX.
[~KurtG] [~aweisberg] wdyt?
> SSTable upgrade should be automatic
> -----------------------------------
>
> Key: CASSANDRA-14197
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14197
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Major
> Fix For: 4.x
>
>
> Upgradesstables should run automatically on node upgrade
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
