thelastpickle / cassandra-reaper

Automated Repair Awesomeness for Apache Cassandra
http://cassandra-reaper.io/
Apache License 2.0
490 stars 218 forks source link

repair_schedule API doc improvement #1042

Open qinjin opened 3 years ago

qinjin commented 3 years ago

Project board link

When scheduling a repair from API, it is not obvious that these two parameters are mandatory:

A successful repair_schedule request looks like:

curl -XPOST "http://localhost:8080/repair_schedule?clusterName=$cluster_name&keyspace=$keyspace&owner=$owner&scheduleDaysBetween=7"

The API doc could be updated to make this more obvious.

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: REAP-112

adejanovski commented 3 years ago

We happily accept PRs 😉

allapavan1208 commented 3 years ago

@adejanovski I am trying to upgrade cass reaper version from 2.0.5 to 2.2.4. When I deployed in staging environment all the previous repair history is gone. Only cluster information and schedules are present. Is there a way to upgrade reaper version with out loosing this historical data(Cassandra is used as backend storage)? If there is any documentation for upgrading the cass reaper can you please share.