[jira] [Commented] (CASSANDRA-11511) disable Anticompaction after repair

["Andrey Vanda (Jira)" <ji...@apache.org>]

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

Andrey Vanda commented on CASSANDRA-11511:
------------------------------------------

I would much appreciate C* Developers is someone clarify the unwanted "anticompaction" behavior after "FULL REPAIR" I have not found any solution - how to avoid any "incremental" style compaction... any timestapm's relation, so on... 

> disable Anticompaction after repair
> -----------------------------------
>
>                 Key: CASSANDRA-11511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11511
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Repair
>            Reporter: Jack Money
>            Priority: Low
>
>  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
(v8.3.4#803005)

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