cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shalom Sagges <>
Subject Re: Reaper v0.6.1 released
Date Thu, 15 Jun 2017 06:30:01 GMT
That's awesome!! Thanks for contributing! 👏👏👏👏👏👏👏

Shalom Sagges
T: +972-74-700-4035
<> <>
<> We Create Meaningful Connections

On Thu, Jun 15, 2017 at 2:32 AM, Jonathan Haddad <> wrote:

> Hey folks!
> I'm proud to announce the 0.6.1 release of the Reaper project, the open
> source repair management tool for Apache Cassandra.
> This release improves the Cassandra backend significantly, making it a
> first class citizen for storing repair schedules and managing repair
> progress.  It's no longer necessary to manage a PostgreSQL DB in addition
> to your Cassandra DB.
> We've been very active since we forked the original Spotify repo.  Since
> this time we've added:
> * A native Cassandra backend
> * Support for versions > 2.0
> * Merged in the WebUI, maintained by Stefan Podkowinski (
> * Support for incremental repair (probably best to avoid till Cassandra
> 4.0, see CASSANDRA-9143)
> We're excited to continue making improvements past the original intent of
> the project.  With the lack of Cassandra 3.0 support in OpsCenter, there's
> a gap that needs to be filled for tools that help with managing a cluster.
> Alex Dejanovski showed me a prototype he recently put together for a really
> nice view into cluster health.  We're also looking to add in support common
> cluster operations like snapshots, upgradesstables, cleanup, and setting
> options at runtime.
> Grab it here:
> Feedback / bug reports / ideas are very much appreciated.
> We have a dedicated, low traffic ML here:
> forum/#!forum/tlp-apache-cassandra-reaper-users
> Jon Haddad
> Principal Consultant, The Last Pickle

This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this 
message or any information herein. 
If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.

View raw message