Reaper Status Update - February 2018
We’ve been a bit quiet on the blog for the last couple months with regard to Reaper status updates. That’s not to say we haven’t been busy, in fact it’s been quite the opposite. We’ve been putting Reaper through it’s paces on fairly large deployments, improving stability, squashing bugs, and exposing more information about the state of the cluster.
The fruit of this effort will be the 1.1 release, which we expect to cut within the next month. The changes in this release were made to improve reliability in one of the largest known deployments of Reaper: a single node managing over 2300 Cassandra nodes across 57 clusters. Working at that sort of scale amplifies even the smallest bugs, and we’re happy to say Reaper 1.1 will work well for deployments of virtually any size.
To make Reaper easier to install, we’ve made RPMs and DEB packages available via Bintray). We’ve linked to them off the Download page. We have a channel for stable and one for the latest builds from the master branch, for those of you that enjoy the latest and greatest. You can see all the packages on the Bintray homepage for The Last Pickle.
We’re very excited for the next release of Reaper. We’ll be sure to update the blog with a more detailed post on our next release!