You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2020/08/21 17:11:00 UTC
[jira] [Commented] (CASSANDRA-15817) Prevent repair from
overrunning compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-15817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182027#comment-17182027 ]
David Capwell commented on CASSANDRA-15817:
-------------------------------------------
Good catch Marcus, thanks for the test. LGTM, checked at the message and the coordinator side. +1
Only comment was https://github.com/krummas/cassandra/commit/546a9587f866cc8f02613b7ff6a93256acd72374#r41670300 which is more an FYI/nit than anything.
> Prevent repair from overrunning compaction
> ------------------------------------------
>
> Key: CASSANDRA-15817
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15817
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Priority: Low
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Repair can run and stream faster than a host can compact. At some point, if a host is sufficiently out of sync, or compaction is especially expensive, it makes sense to intentionally block repair so that compaction can catch up
--
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