Re: Reaper as cassandra-admin
As an aside, it’s frustrating that ya’ll would sit on this for months (first e-mail was April); you folks have enough people that know the process to know that communicating early and often helps avoid duplicating (expensive) work.
The best tech needs to go in and we need to leave ourselves with the ability to meet the goals of the original proposal (and then some). The reaper UI is nice, I wish you’d have talked to the other group of folks to combine efforts in April, we’d be much further ahead.
> On Aug 27, 2018, at 6:02 PM, Jeff Jirsa <jjirsa@xxxxxxxxx> wrote:
> Can you get all of the contributors cleared?
> What’s the architecture? Is it centralized? Is there a sidecar?
>> On Aug 27, 2018, at 5:36 PM, Jonathan Haddad <jon@xxxxxxxxxxxxx> wrote:
>> Hey folks,
>> Mick brought this up in the sidecar thread, but I wanted to have a clear /
>> separate discussion about what we're thinking with regard to contributing
>> Reaper to the C* project. In my mind, starting with Reaper is a great way
>> of having an admin right now, that we know works well at the kind of scale
>> we need. We've worked with a lot of companies putting Reaper in prod (at
>> least 50), running on several hundred clusters. The codebase has evolved
>> as a direct result of production usage, and we feel it would be great to
>> pair it with the 4.0 release. There was a LOT of work done on the repair
>> logic to make things work across every supported version of Cassandra, with
>> a great deal of documentation as well.
>> In case folks aren't aware, in addition to one off and scheduled repairs,
>> Reaper also does cluster wide snapshots, exposes thread pool stats, and
>> visualizes streaming (in trunk).
>> We're hoping to get some feedback on our side if that's something people
>> are interested in. We've gone back and forth privately on our own
>> preferences, hopes, dreams, etc, but I feel like a public discussion would
>> be healthy at this point. Does anyone share the view of using Reaper as a
>> starting point? What concerns to people have?
>> Jon Haddad
>> twitter: rustyrazorblade
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx