node re-start delays , busy Deleting mc-txn-compaction/ Adding log file replica

2019-06-18 Thread ZAIDI, ASAD A
I’m on environment with apache Cassandra 3.11.1 with java 1.8.0_144. One Node went OOM and crashed. Re-starting this crashed node is taking long time. Trace level debug log is showing messages like: Debug.log trace excerpt: TRACE [main] 2019-06-18 21:30:43,449 LogTr

Re: Compaction resume after node restart and upgrade

2019-06-18 Thread Jeff Jirsa
> On Jun 18, 2019, at 12:53 AM, Oleksandr Shulgin > wrote: > >> On Tue, Jun 18, 2019 at 3:08 AM Jeff Jirsa wrote: > >> Yes - the incomplete sstable will be deleted during startup (in 3.0 and >> newer there’s a transaction log of each compaction in progress - that gets >> cleaned during th

Re: Cassandra Tombstone

2019-06-18 Thread Oleksandr Shulgin
On Tue, Jun 18, 2019 at 8:06 AM ANEESH KUMAR K.M wrote: > > I am using Cassandra cluster with 3 nodes which is hosted on AWS. Also we > have NodeJS web Application which is on AWS ELB. Now the issue is that, > when I add 2 or more servers (nodeJS) in AWS ELB then the delete queries > are not work

Re: Compaction resume after node restart and upgrade

2019-06-18 Thread Oleksandr Shulgin
On Tue, Jun 18, 2019 at 3:08 AM Jeff Jirsa wrote: > Yes - the incomplete sstable will be deleted during startup (in 3.0 and > newer there’s a transaction log of each compaction in progress - that gets > cleaned during the startup process) > Wait, does that mean that in pre-3.0 versions one can