0.7.0-beta-25082017

Binaries for the 0.7.0 fault tolerant version of Reaper.
This version allows running several Reaper instances sharing the same Cassandra backend, and offers full support for multi DC clusters.

0.6.2

Changelog :

• Fix coordinator node being nulled by abort() in incremental repairs
• Added delete-schedule to the cli (spreaper)
• Allow schedules for both full and incremental repairs on the same keyspace
• Fix ClassCastException when using H2 backend
• Fix SSL encryption communications through JMX
• Fix cluster/rack names with dashes in the UI
• Fix down status not being correctly caught by Reaper when nodes aren't cleanly stopped
• Add docker-compose environment to build packages (jar, deb and rpm)

0.6.1

Changelog :

• Fix for storing run history in schedules with the Postgres/H2 backends

0.6.0

Changelog :

• New data model for the Cassandra backend - huge performance optimizations for this backend
• Fix parallel repair computation for clusters with vnodes
• Minimum wait time between segments is now configurable
• Added an optional query logger for the Cassandra backend

0.5.0 - Autoscheduling and seed dynamic discovery

Changelog :

• Add configurable auto-scheduling of repairs for all (non system) keyspaces
• Fix bad segment count display on scheduled repairs
• Add dynamic discovery of seeds for clusters

0.4.1 - Fix for computing active/pending repairs in 2.2+

The JMX Mbeans used to check the number of active and pending repair sessions has changed in Cassandra 2.2, making Reaper unable to check if a repair is already running before running a new segment.

This release fixes the issue by using the right MBean depending on the version of Cassandra.
It also adds a check to prevent running new segments on nodes that are performing validation compaction, and raise the timeout for each segments when running incremental repair (there's one "fake" segment per node in incremental repair, which may take longer than 30mn due to anticompaction).