Re: Reaper as cassandra-admin
I don't believe #1 should be an issue, Mick has been reaching out.
Alex and Mick are putting together some architecture documentation, I won't
step on their toes. Currently you can run Reaper as a single instance that
connects to your entire cluster, multiple instances in HA mode, and we're
finishing up the rework of the code to run it as a sidecar.
On Mon, 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
> > of having an admin right now, that we know works well at the kind of
> > 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,
> > 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
> > be healthy at this point. Does anyone share the view of using Reaper as
> > starting point? What concerns to people have?
> > --
> > Jon Haddad
> > http://www.rustyrazorblade.com
> > twitter: rustyrazorblade
> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx