You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sagar Linge (Jira)" <ji...@apache.org> on 2020/09/03 09:57:00 UTC
[jira] [Commented] (CASSANDRA-13885) Allow to run full repairs in
3.0 without additional cost of anti-compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-13885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190016#comment-17190016 ]
Sagar Linge commented on CASSANDRA-13885:
-----------------------------------------
What was the solution implemented for this issue ?
I am facing same issue in cassandra 3.11 .
> Allow to run full repairs in 3.0 without additional cost of anti-compaction
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-13885
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13885
> Project: Cassandra
> Issue Type: Bug
> Reporter: Thomas Steinmaurer
> Priority: Normal
>
> This ticket is basically the result of the discussion in Cassandra user list: https://www.mail-archive.com/user@cassandra.apache.org/msg53562.html
> I was asked to open a ticket by Paulo Motta to think about back-porting running full repairs without the additional cost of anti-compaction.
> Basically there is no way in 3.0 to run full repairs from several nodes concurrently without troubles caused by (overlapping?) anti-compactions. Coming from 2.1 this is a major change from an operational POV, basically breaking any e.g. cron job based solution kicking off -pr based repairs on several nodes concurrently.
--
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