Re: Data Loss irreparabley so

2017-08-02 Thread kurt greaves
You should run repairs every GC_GRACE_SECONDS. If a node is overloaded/goes down, you should run repairs. LOCAL_QUORUM will somewhat maintain consistency within a DC, but certainly doesn't mean you can get away without running repairs. You need to run repairs even if you are using QUORUM or ONE.​

Re: Data Loss irreparabley so

2017-07-27 Thread Jon Haddad
We (The Last Pickle) maintain an open source tool to help manage repairs across your clusters called Reaper. It’s a lot easier to set up and manage than trying to manage it through cron. http://thelastpickle.com/reaper.html > On Jul 27, 2017, at 12:38 AM,

Re: Data Loss irreparabley so

2017-07-27 Thread Daniel Hölbling-Inzko
In that vein, Cassandra support Auto compaction and incremental repair. Does this mean I have to set up cron jobs on each node to do a nodetool repair or is this taken care of by Cassandra anyways? How often should I run nodetool repair Greetings Daniel Jeff Jirsa schrieb am

Re: Data Loss irreparabley so

2017-07-26 Thread Jeff Jirsa
On 2017-07-25 15:49 (-0700), Roger Warner wrote: > This is a quick informational question. I know that Cassandra can detect > failures of nodes and repair them given replication and multiple DC. > > My question is can Cassandra tell if data was lost after a failure

Re: Data Loss irreparabley so

2017-07-25 Thread kurt greaves
Cassandra doesn't do any automatic repairing. It can tell if your data is inconsistent, however it's really up to you to manage consistency through repairs and choice of consistency level for queries. If you lose a node, you have to manually repair the cluster after replacing the node, but really