cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Scott Andreas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11511) disable Anticompaction after repair
Date Mon, 19 Nov 2018 02:35:00 GMT

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

C. Scott Andreas updated CASSANDRA-11511:
-----------------------------------------
    Component/s: Repair

> disable Anticompaction after repair
> -----------------------------------
>
>                 Key: CASSANDRA-11511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11511
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Repair
>            Reporter: Jack Money
>            Priority: Minor
>
>  I use write consistency level ALL.
> Sometimes when my data grows to fast i cant normal add new node, [CASSANDRA-10797 issue
occurs|https://issues.apache.org/jira/browse/CASSANDRA-10797].
> After this i set auto_bootstrap to false, and run nodetool repair - full on all tables
one by one.
> 70% percent time of repair is taken by "Anticompaction after repair".
> But i don't need it, because i do not need to run repair (consistency level ALL.). 
> To avoid anticompaction i run repair with token range [Avoid anticompaction when doing
subrange repair|https://issues.apache.org/jira/browse/CASSANDRA-10422] but i think it should
be options to avoid anticompaction, i.e. nodetool repair -full *-disableanticompaction* 




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message