You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Cassandra 4.1 incremental repair is now default repair type, however, documentation still recommends running full-repair occasionally. However, since Reaper only schedules one kind of repair (either incremental or full), how a user would have to introduce some manual intervention to run both using a single schedule.
What this client would like to do is use Reaper for scheduling repair and include both incremental and full in the same schedule so that x number of incremental repairs is then followed by a full-repair like what the documentation suggests.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: REAP-19
The text was updated successfully, but these errors were encountered:
Project board link
In Cassandra 4.1 incremental repair is now default repair type, however, documentation still recommends running full-repair occasionally. However, since Reaper only schedules one kind of repair (either incremental or full), how a user would have to introduce some manual intervention to run both using a single schedule.
What this client would like to do is use Reaper for scheduling repair and include both incremental and full in the same schedule so that x number of incremental repairs is then followed by a full-repair like what the documentation suggests.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: REAP-19
The text was updated successfully, but these errors were encountered: