cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13425) nodetool refresh should try to insert new sstables in existing leveling
Date Fri, 07 Apr 2017 12:31:41 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Eriksson updated CASSANDRA-13425:
----------------------------------------
    Status: Patch Available  (was: Open)

https://github.com/krummas/cassandra/commits/marcuse/nodetoolrefresh

Uses the same approach as tools/bin/sstableofflinerelevel - it sorts the sstables by last
token to get the smallest (by token range) sstables first, then tries to insert them in the
leveling, starting with the highest populated level.

> 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.3.15#6346)

Mime
View raw message