race_seconds to zero? ) and let compaction take
> care of tombstone before sstable migration. Do keep an eye on hinted
> handoffs because of zero’ed gc_grace_second property.
>
>
>
>
>
> *From:* Muralikrishna Gutha [mailto:muralikgu...@gmail.com]
> *Sent:* T
list saves ordering where you append or prepend the value into the list.
> A list allows duplicates.
>
>
>
>
>
>
>
> *From:* Muralikrishna Gutha [mailto:muralikgu...@gmail.com]
> *Sent:* Thursday, October 24, 2019 10:27 AM
> *To:* user@cassandra.apache.org
> *Cc:* M
Hello Guys,
We started noticing strange behavior after we migrated one keyspace from
existing cluster to new cluster.
We expanded our source cluster from 18 node to 36 nodes and Didn't run
"nodetool cleanup".
We took sstable backups on source cluster and restored which has duplicate
data and rest
We are running Cassandra: 2.1.15, We started noticing below errors, app is
writing larger mutations and before we take a route of increasing from 32MB to
64MB for `commitlog_segment_size_in_mb` wanted to understand if there are any
cons by increasing it. Do we need to tweak any other parameters
