search

spotify / cassandra-reaper

Software to run automated repairs of cassandra
235 stars 60 forks source link

Keep raeper state inside Cassandra #104

Open nathan-gs opened 9 years ago

nathan-gs commented 9 years ago

Instead of relying on a outside data source, like Postgres, it would make sense to keep the state inside Cassandra, in a separate keyspace.

Bj0rnen commented 9 years ago

There would be 2 ways to go about this, when using one Reaper for many clusters:

The first one is pretty straight-forward. It's just another implementation of IStorage.

The second option is also clearly possible, considering there is no cross-cluster state. Except the info of which clusters there are, which would now be moved to the config. But it would not play well with IStorage, since Reaper wouldn't know how to map IDs to clusters. Either all clusters would have to be asked, or a bigger rewrite would be needed to accommodate for this.

Which one of these options did you have in mind?

nathan-gs commented 9 years ago

The second option would have my preference.

Option 1 would also work in the mean time, especially if it can be the same cluster as it's monitoring.

yingzong commented 8 years ago

I disagree. It is a bad idea for any maintenance state to be stored in the system being maintained. It should be totally independent. DataStax's OpsCenter made that grievous mistake.