Only sstables at unrepaired state go through anticompaction.
Le lun. 9 nov. 2020 à 07:01, manish khandelwal
a écrit :
> Thanks Alex.
>
> One more query, all are sstables (repaired + unrepaired ) part of
> anti-compaction? We are using full repair with -pr option.
>
> Regards
> Manish
>
> On
Thanks Alex.
One more query, all are sstables (repaired + unrepaired ) part of
anti-compaction? We are using full repair with -pr option.
Regards
Manish
On Mon, Nov 9, 2020 at 11:17 AM Alexander DEJANOVSKI
wrote:
> Hi Manish,
>
> Anticompaction is the same whether you run full or incremental
Hi,
You have two options to disable anticompaction when running full repair:
- add the list of DCs using the --dc flag (even if there's just a single DC
in your cluster)
- Use subrange repair, which is done by tools such as Reaper (it can be
challenging to do it yourself on a vnode cluster).
Hi Manish,
Anticompaction is the same whether you run full or incremental repair.
Le ven. 6 nov. 2020 à 04:37, manish khandelwal
a écrit :
> In documentation it is given that while running incremental repairs, anti
> compaction is done which results in repaired and unrepaired sstables. Since
Hi Team,
In Cassandra 3.x, Anti-compaction is performed after repair (incremental or
full). Repair does not have any way to bypass anti-compaction (if not
running sub range repair with -st & -et). Here is a jira ticket.
https://issues.apache.org/jira/browse/CASSANDRA-11511
I am facing 100% disk