Re: Yet another repair solution
Great to see that there is an interest! As there currently are some internal dependencies etc. in place there is still some work to be done before we can publish it. I would expect this to take at least a few weeks, to try set the correct expectations.
On tis, 2018-08-28 at 23:18 -0700, Vinay Chella wrote:
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.
On Tue, Aug 28, 2018 at 1:23 PM Roopa <firstname.lastname@example.org<mailto:email@example.com>>
+1 interested in seeing and understanding another repair solution.
On Aug 28, 2018, at 1:03 PM, Joseph Lynch <joe.e.lynch@xxxxxxxxx<mailto:joe.e.lynch@xxxxxxxxx>> 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
compare notes and figure out the best way to implement that kind of
On Tue, Aug 28, 2018 at 6:34 AM Marcus Olsson <
With the risk of stirring the repair/side-car topic even further I'd
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
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx<mailto:dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx>
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx<mailto:dev-help@xxxxxxxxxxxxxxxxxxxx>