[
https://issues.apache.org/jira/browse/CASSANDRA-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081166#comment-16081166
]
Paulo Motta edited comment on CASSANDRA-13425 at 7/10/17 9:16 PM:
------------------------------------------------------------------
Had a quick peek at this and was wondering if we really need to pollute the
{{AbstractCompactionStrategy}} inteface with a strategy-specific method
{{setBestLevelsOn}} and if we couldn't do that logic to
{{LeveledCompactionStrategy.addSSTables}} instead?
was (Author: pauloricardomg):
Had a quick peek at this and was wondering if we really need to pollute the
{{AbstractCompactionStrategy}} inteface with a strategy-specific method
{{setBestLevelsOn}} and was wondering if we couldn't do that logic to
{{LeveledCompactionStrategy.addSSTables}} instead?
> 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: [email protected]
For additional commands, e-mail: [email protected]
