Hi, The first step in using reaper is to add a cluster to it, as it is a tool that can manage multiple clusters and does not need to be executed on a Cassandra node (you can run in on any edge node you want).
You should run : ./bin/spreaper add-cluster 127.0.0.1 Where you'll replace 127.0.0.1 by the address of one of the nodes of your cluster. Then you can run : ./bin/spreaper cluster_name keyspace_name to start repairing a keyspace. You might want to drop in the UI made by Stefan Podkowinski which might ease things up for you, at least at the beginning : https://github.com/spodkowinski/cassandra-reaper-ui Worth mentioning that at The Last Pickle we maintain a fork of Reaper that handles incremental repair, works with C* 2.x and 3.0, and bundles the UI : https://github.com/thelastpickle/cassandra-reaper We have a branch that allows using Cassandra as a storage backend instead of Postgres : https://github.com/thelastpickle/cassandra-reaper/tree/add-cassandra-storage It should be merged to master really soon and should be ready to use. Cheers, On Tue, Nov 1, 2016 at 1:45 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello, > > Has anyone played around with the cassandra reaper ( > https://github.com/spotify/cassandra-reaper)? > > if so can some please help me with the set-up, I can't get it working. I > used the below steps: > > 1. create jar file using maven > 2. java -jar cassandra-reaper-0.2.3-SNAPSHOT.jar server > cassandra-reaper.yaml > 3. ./bin/spreaper repair production users > -- ----------------- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com
