Hi Tom, Do you use any collections on this column family? We've had issues in the past with unexpectedly large partitions reported on data models with collections, which can also generate tons of tombstones on UPDATE ( https://issues.apache.org/jira/browse/CASSANDRA-10547)
--Bryan On Mon, Mar 7, 2016 at 11:23 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Sat, Mar 5, 2016 at 9:16 AM, Tom van den Berge <t...@drillster.com> > wrote: > >> I don't think compression can be the cause of the difference, because of >> two reasons: >> > > Your two reasons seem legitimate. > > Though you say you do not frequently do DELETE and so it shouldn't be due > to tombstones, there are semi-recent versions of Cassandra which create a > runaway avalanche of tombstones that double every time they are compacted. > What version are you running? > > Also, is there some reason you are not just dumping the table with > sstable2json and inspecting the contents of the row in question? > > =Rob > > > >
