You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2023/09/12 16:57:00 UTC
[jira] [Comment Edited] (CASSANDRA-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764294#comment-17764294 ]
Caleb Rackliffe edited comment on CASSANDRA-18816 at 9/12/23 4:56 PM:
----------------------------------------------------------------------
+1 to the trunk patch
(Let me know if 5.0 is significantly different)
(For the record, I'd support getting this into 5.0.)
was (Author: maedhroz):
+1 to the trunk patch
(Let me know if 5.0 is significantly different)
> Add support for repair coordinator to retry messages that timeout
> -----------------------------------------------------------------
>
> Key: CASSANDRA-18816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18816
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> Now that CASSANDRA-15399 is in, most of the repair messages have a state that they can check against to make message delivery idempotent, allowing the coordinator to retry such messages; a few of the most critical messages to retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and SYNC_RSP.
> With this I propose making the coordinator able to retry these key messages to try and make repair more resilient to ephemeral issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org