cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13425) nodetool refresh should try to insert new sstables in existing leveling
Date Wed, 05 Jul 2017 21:14:00 GMT

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

Ariel Weisberg commented on CASSANDRA-13425:
--------------------------------------------

I added some questions. Seems reasonable enough although there are some n ^ 2 array list removal
steps. The question is do we ever work with enough tables for it to matter and how long can
this take before it's too long? 

I also wonder if it's an issue placing these new tables in the highest level since it means
new updates will take even longer to reach them.

> 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


Mime
View raw message