[jira] [Commented] (CASSANDRA-13425) nodetool refresh should try to insert new sstables in existing leveling

["Tom Petracca (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277478#comment-16277478 ] 

Tom Petracca commented on CASSANDRA-13425:
------------------------------------------

Maybe a topic for a separate ticket, but thoughts on adding a version of {{ColumnFamilyStore.loadNewSSTables}} that assumes (and maybe even validates) that there are no existing SSTables on disk? Thus instead of having to force things down into level 0 and then attempt to insert them where they fit, can just blindly use the levels from the new tables being loaded.

Use case here is that I load new sstables on restore from a backup (set tokens -> turn on cluster -> write schemas -> copy in sstables from snapshot -> reload sstables). I know going into the process that I'll have no conflicts because target table is empty.

> nodetool refresh should try to insert new sstables in existing leveling
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-13425
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13425
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 4.x
>
>
> Currently {{nodetool refresh}} sets level to 0 on all new sstables, instead we could try to find gaps in the existing leveling and insert them there.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org