not indicate any "connection" via
service or jmx port :)
So now need to see why the data is not getting purged.
Thanks again!!
From: kurt greaves <k...@instaclustr.com>
Date: Wednesday, January 31, 2018 at 11:27 PM
To: User <user@cassandra.apache.org>
Subject: Re: TWCS not del
36 Jan 29 21:53 mc-139-big-Index.db
>
> -rw-rw-r--. 1 vchadoop vchadoop 5055 Jan 29 21:53
> mc-139-big-Statistics.db
>
> -rw-rw-r--. 1 vchadoop vchadoop 56 Jan 29 21:53 mc-139-big-Summary.db
>
> -rw-rw-r--. 1 vchadoop vchadoop 92 Jan 29 21:53 mc-139-big-TOC.txt
>
e: Tuesday, January 30, 2018 at 7:37 AM
To: <user@cassandra.apache.org>
Subject: RE: TWCS not deleting expired sstables
Wow! It’s in the DataStax documentation:
https://docs.datastax.com/en/dse/5.1/dse-admin/datastax_enterprise/tools/toolsSStables/toolsSStabExpiredBlockers.html
Othe
/toolsSSTableUtilitiesTOC.html
Kenneth Brotman
From: kurt greaves [mailto:k...@instaclustr.com]
Sent: Monday, January 29, 2018 8:20 PM
To: User
Subject: Re: TWCS not deleting expired sstables
Likely a read repair caused old data to be brought into a newer SSTable. Try
running sstableexpiredblockers
Likely a read repair caused old data to be brought into a newer SSTable.
Try running sstableexpiredblockers to find out if there's a newer SSTable
blocking that one from being dropped.
stable, so there is no
dependency or delay caused from other sstables.
Thanks,
Jayesh
From: <brian.spind...@gmail.com>
Date: Sunday, January 28, 2018 at 1:02 PM
To: <user@cassandra.apache.org>
Subject: Re: TWCS not deleting expired sstables
I would start here: http://thelastpickle.co
I would start here: http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html
Specifically the “Hints and repairs” and “Timestamp overlap” sections might be
of use.
-B
> On Jan 25, 2018, at 11:05 AM, Thakrar, Jayesh
> wrote:
>
> Wondering if I can get some