I noticed that I am not able to add schedules, but I can run repairs. Is there some limitation on the opensource for adding the schedules?
On Mon, Nov 21, 2016 at 4:25 PM, Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello Alexander, > > Thanks for the help, I couldn't get around with my issue. > but I started using : https://github.com/thelastpickle/cassandra-reaper > it works like a charm :) > > I am using GUI, I just need to tweak/play with the configuration. > > Thanks again for the help > > > On Tue, Nov 1, 2016 at 12:26 PM, Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> ok thank you, >> I will try and update you. >> >> On Tue, Nov 1, 2016 at 10:57 AM, Alexander Dejanovski < >> a...@thelastpickle.com> wrote: >> >>> Running reaper with INFO level logging (that can be configured in the >>> yaml file), you should have a console output telling you what's going on. >>> >>> If you started reaper with memory back end, restarting it will reset it >>> and you'll have to register your cluster again, but if you used postgres it >>> will resume tasks where they were left off. >>> >>> Please restart Reaper to at least have an output we can get information >>> from, otherwise we're blind. >>> >>> Since you're using Cassandra 2.1, I'd advise switching to our fork since >>> the original one is compiled against Cassandra 2.0 libraries. If you switch >>> and use postgres, make sure you update the schema accordingly as we added >>> fields for incremental repair support. >>> >>> Cheers, >>> >>> Le mar. 1 nov. 2016 18:31, Jai Bheemsen Rao Dhanwada < >>> jaibheem...@gmail.com> a écrit : >>> >>>> Cassandra version is 2.1.16 >>>> >>>> In my setup I don't see it is writting to any logs >>>> >>>> On Tue, Nov 1, 2016 at 10:25 AM, Alexander Dejanovski < >>>> a...@thelastpickle.com> wrote: >>>> >>>> Do you have anything in the reaper logs that would show a failure of >>>> some sort ? >>>> Also, can you tell me which version of Cassandra you're using ? >>>> >>>> Thanks >>>> >>>> On Tue, Nov 1, 2016 at 6:15 PM Jai Bheemsen Rao Dhanwada < >>>> jaibheem...@gmail.com> wrote: >>>> >>>> Thanks Alex, >>>> >>>> Forgot to mention but I did add the cluster. See the status below. It >>>> says the status is running but I don't see any repair happening. this is in >>>> the same state from past 1 days. >>>> b/w there not much of data in cluster. >>>> >>>> [root@machine cassandra-reaper]# ./bin/spreaper status-repair 3 >>>> # Report improvements/bugs at https://github.com/spotify/cas >>>> sandra-reaper/issues >>>> # ------------------------------------------------------------ >>>> ------------------ >>>> # Repair run with id '3': >>>> { >>>> "cause": "manual spreaper run", >>>> "cluster_name": "production", >>>> "column_families": [], >>>> "creation_time": "2016-11-01T00:39:15Z", >>>> "duration": null, >>>> "end_time": null, >>>> "estimated_time_of_arrival": null, >>>> "id": 3, >>>> "intensity": 0.900, >>>> "keyspace_name": "users", >>>> * "last_event": "no events",* >>>> "owner": "root", >>>> "pause_time": null, >>>> "repair_parallelism": "DATACENTER_AWARE", >>>> "segments_repaired": 0, >>>> "start_time": "2016-11-01T00:39:15Z", >>>> * "state": "RUNNING",* >>>> "total_segments": 301 >>>> } >>>> [root@ machine cassandra-reaper]# >>>> >>>> On Tue, Nov 1, 2016 at 9:24 AM, Alexander Dejanovski < >>>> a...@thelastpickle.com> wrote: >>>> >>>> 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/thelastpi >>>> ckle/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 >>>> >>>> >>>> -- >>>> ----------------- >>>> Alexander Dejanovski >>>> France >>>> @alexanderdeja >>>> >>>> Consultant >>>> Apache Cassandra Consulting >>>> http://www.thelastpickle.com >>>> >>>> >>>> -- >>> ----------------- >>> Alexander Dejanovski >>> France >>> @alexanderdeja >>> >>> Consultant >>> Apache Cassandra Consulting >>> http://www.thelastpickle.com >>> >> >> >
