I am excited to see that the community is working on solving the critical problems in C* operations (e.g., repair, backups etc.,) with different solutions. Of course, learnings from these systems are key to designing the robust solution which works for everyone.
Thanks, Vinay Chella On Tue, Aug 28, 2018 at 1:23 PM Roopa <rtangir...@netflix.com.invalid> wrote: > +1 interested in seeing and understanding another repair solution. > > > On Aug 28, 2018, at 1:03 PM, Joseph Lynch <joe.e.ly...@gmail.com> wrote: > > > > I'm pretty interested in seeing and understanding your solution! When we > > started on CASSANDRA-14346 reading your design documents and plan you > > sketched out in CASSANDRA-10070 were really helpful in improving our > > design. I'm particularly interested in how the Scheduler/Job/Task APIs > > turned out (we're working on something similar internally and would love > to > > compare notes and figure out the best way to implement that kind of > > abstraction)? > > > > -Joey > > > > > > On Tue, Aug 28, 2018 at 6:34 AM Marcus Olsson < > marcus.ols...@ericsson.com> > > wrote: > > > >> Hi, > >> > >> With the risk of stirring the repair/side-car topic even further I'd > just > >> like to mention that we have recently gotten approval to contribute our > >> repair management side-car solution. > >> It's based on the proposal in > >> https://issues.apache.org/jira/browse/CASSANDRA-10070 as a standalone > >> application sitting next to each instance. > >> With the recent discussions in mind I'd just like to hear the thoughts > >> from the community on this before we put in the effort of bringing our > >> solution into open source. > >> > >> Would there be an interest of having yet another repair solution in the > >> discussion? > >> > >> Best Regards > >> Marcus Olsson > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
