Cool, moving this from dev list to JIRA, will start breaking down tasks and
document my progress there
https://issues.apache.org/jira/browse/CASSANDRA-16909
> On Aug 27, 2021, at 1:21 PM, David Capwell wrote:
>
> Push vs pull isn’t too critical, but there is one edge case to consider; if
>
Push vs pull isn’t too critical, but there is one edge case to consider; if we
didn’t think the participate got restarted triggering validation again (which
may have caused the process to end) could be a problem.
> On Aug 26, 2021, at 9:50 AM, Yifan Cai wrote:
>
>>
>> 2. Add retries to
>
> 2. Add retries to specific stages of coordination, such as prepare and
>validate. In order to do these retries we first need to know what the
state is for the participant which has yet to reply...
If I understand it correctly, does it mean retries only happen in the
coordinator and
+1 from me, any improvement in this area would be great.
It would be nice if this could include visibility into repair streams, but just
exposing the repair state will be a big improvement.
> On Aug 25, 2021, at 5:46 PM, David Capwell wrote:
>
> Now that 4.0 is out, I want to bring up
Now that 4.0 is out, I want to bring up improving repair again (earlier
thread
http://mail-archives.apache.org/mod_mbox/cassandra-commits/201911.mbox/%3cjira.13266448.1572997299000.99567.1572997440...@atlassian.jira%3E),
specifically the following two JIRAs:
CASSANDRA-15566 - Repair coordinator
