Re: [Discuss] Repair inside C*

Thanks, Josh. I've just updated the CEP and included all the solutions you mentioned below. Jaydeep On Thu, Feb 22, 2024 at 9:33 AM Josh McKenzie wrote: > Very late response

Re: [Discuss] Repair inside C*

There are already some community solutions to scheduled repairs like this (1), it runs along Cassandra node though ... anyway. I would like to see that we pick what is the best already out there and try to integrate it rather than trying to figure it all out again. That seems like a waste of time

Re: [Discuss] Repair inside C*

> we're all willing to bikeshed for our personal preference on where it lives > and how it's implemented, and at the end of the day, code talks. I don't > think anyone's said they'll die on the hill of implementation details :D I don't think we're going to be able to reach a consensus on an

Re: [Discuss] Repair inside C*

Apologies, I just read the previous message and missed the previous discussion on sidecar vs main process on this thread. :-) It does not look like a final agreement was reached about this and there are lots of good arguments for both sides, but perhaps it would be nice to agree on this before a

Re: [Discuss] Repair inside C*

+1 to Josh's points, The project has considered native repair scheduling for a long time but it was never made a reality due to the complex considerations involved and availability of custom implementations/tools like cassandra-reaper, which is a popular way of scheduling repairs in Cassandra.

Re: [Discuss] Repair inside C*

Very late response from me here (basically necro'ing this thread). I think it'd be useful to get this condensed into a CEP that we can then discuss in that format. It's clearly something we all agree we need and having an implementation that works, even if it's not in your preferred execution

Re: [Discuss] Repair inside C*

Is anyone going to file an official CEP for this? As mentioned in this email thread, here is one of the solution's design doc and source code on a private Apache Cassandra patch. Could you

Re: [Discuss] Repair inside C*

> That said I would happily support an effort to bring repair scheduling to the > sidecar immediately. This has nothing blocking it, and would potentially > enable the sidecar to provide an official repair scheduling solution that is > compatible with current or even previous versions of the

Re: [Discuss] Repair inside C*

> The idea that your data integrity needs to be opt-in has never made sense to > me from the perspective of either the product or the end user. I could not agree with this more. 100%. > The current (and past) state of things where running the DB correctly > **requires* *running a separate

Re: [Discuss] Repair inside C*

I agree that it would be ideal for Cassandra to have a repair scheduler in-DB. That said I would happily support an effort to bring repair scheduling to the sidecar immediately. This has nothing blocking it, and would potentially enable the sidecar to provide an official repair scheduling

Re: [Discuss] Repair inside C*

I concur, repair is an intrinsic part of the database and belongs inside it. We can certainly expose a REST control plane API via the sidecar for triggering it on demand, scheduling, etc. That said, there are various implementation of repair scheduling and orchestration that a lot of

Re: [Discuss] Repair inside C*

I'm 100% in favor of repair being part of the core DB, not the sidecar. The current (and past) state of things where running the DB correctly *requires* running a separate process (either community maintained or official C* sidecar) is incredibly painful for folks. The idea that your data

Re: [Discuss] Repair inside C*

gt;>> mailto:dev@cassandra.apache.org>> wrote: >>>> In [2] we suggested that the next step should be a CEP. >>>> >>>> I am happy to lend a hand to this effort as well. >>>> >>>> Thanks Jaydeep and David - really appreciated. >&

Re: [Discuss] Repair inside C*

eciated. >>> >>> German >>> >>> -- >>> *From:* David Capwell >>> *Sent:* Tuesday, July 25, 2023 8:32 AM >>> *To:* dev >>> *Cc:* German Eichberger >>> *Subject:* [EXTERNAL]

Re: [Discuss] Repair inside C*

>> German >> >> -- >> *From:* David Capwell >> *Sent:* Tuesday, July 25, 2023 8:32 AM >> *To:* dev >> *Cc:* German Eichberger >> *Subject:* [EXTERNAL] Re: [Discuss] Repair inside C* >> >> As someone who has done a l

Re: [Discuss] Repair inside C*

effort as well. > > Thanks Jaydeep and David - really appreciated. > > German > > -- > *From:* David Capwell > *Sent:* Tuesday, July 25, 2023 8:32 AM > *To:* dev > *Cc:* German Eichberger > *Subject:* [EXTERNAL] Re: [Discuss] Repair ins

Re: [Discuss] Repair inside C*

: [EXTERNAL] Re: [Discuss] Repair inside C* As someone who has done a lot of work trying to make repair stable, I approve of this message ^_^ More than glad to help mentor this work On Jul 24, 2023, at 6:29 PM, Jaydeep Chovatia wrote: To clarify the repair solution timing, the one we have listed

Re: [Discuss] Repair inside C*

As someone who has done a lot of work trying to make repair stable, I approve of this message ^_^ More than glad to help mentor this work > On Jul 24, 2023, at 6:29 PM, Jaydeep Chovatia > wrote: > > To clarify the repair solution timing, the one we have listed in the article > is not the

Re: [Discuss] Repair inside C*

To clarify the repair solution timing, the one we have listed in the article is not the recently developed one. We were hitting some high-priority production challenges back in early 2018, and to address that, we developed and rolled out the solution in production in just a few months. The

Re: [Discuss] Repair inside C*

Hi German, The goal is always to backport our learnings back to the community. For example, I have already successfully backported the following two enhancements/bug fixes back to the Open Source Cassandra, which are described in the article. I am already currently working on open-source a few

[Discuss] Repair inside C*

All, We had a brief discussion in [2] about the Uber article [1] where they talk about having integrated repair into Cassandra and how great that is. I expressed my disappointment that they didn't work with the community on that (Uber, if you are listening time to make amends ) and it turns