Re: Corrupted commit log prevents Cassandra start

If you already have a regular cadence of repair then you can set "commit_failure_policy" to ignore in cassandra.yaml. So that C* process does not crash on corrupt commit log. On Fri, Jul 7, 2017 at 2:10 AM, Hannu Kröger wrote: > Hello, > > yes, that’s what we do when things

Re: "nodetool repair -dc"

I do not see the need to run repair, as long as cluster was in healthy state on adding new nodes. On Fri, Jul 7, 2017 at 8:37 AM, vasu gunja wrote: > Hi , > > I have a question regarding "nodetool repair -dc" option. recently we > added multiple nodes to one DC center, we

Re: Starting Cassandrs after restore of Data - get error

Use "dos2unix" utility when editing/moving from windows to Linux -- could be a formatting issue Subroto > On Jul 7, 2017, at 9:47 AM, Jonathan Baynes > wrote: > > Yes both clusters match I've checked 3 Times and diff'd it as well. Would > file format have any

Re: Deflate compressor

*"Decrease tombstone_compaction_interval and decrease tombstone_threshold, or set unchecked_tombstone_compaction to true to ignore both conditions and collect based /purely on gc grace/."* Is this actually true for C* version 3.11.0? AND compaction = {'class':