[ https://issues.apache.org/jira/browse/CASSANDRA-10547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241742#comment-15241742 ]
Alex Petrov commented on CASSANDRA-10547: ----------------------------------------- You can upgrade to (at least) 2.1.13, the issue doesn't appear on it anymore. I've ran similar tests against 2.1.5 and 2.1.13. 2.1.5: {code} Read 1 live and 23 tombstoned cells [SharedPool-Worker-3] | 2016-04-14 21:05:09.391000 | 127.0.0.1 | {code} 2.1.13 {code} Read 1 live and 0 tombstone cells [SharedPool-Worker-3] | 2016-04-14 21:01:01.666000 | 127.0.0.1 | {code} Issue doesn't appear on {3.x} either. > Updating a CQL List many times creates many tombstones > ------------------------------------------------------- > > Key: CASSANDRA-10547 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10547 > Project: Cassandra > Issue Type: Bug > Environment: Cassandra 2.1.9, Java driver 2.1.5 > Reporter: James Bishop > Assignee: Alex Petrov > Attachments: tombstone.snippet > > > We encountered a TombstoneOverwhelmingException in cassandra system.log which > caused some of our CQL queries to fail. > We are able to reproduce this issue by updating a CQL List column many times. > The number of tombstones created seems to be related to (number of list items > * number of list updates). We update the entire list on each update using the > java driver. (see attached code for details) > Running nodetool compact does not help, but nodetool flush does. It appears > that the tombstones are being accumulated in memory. > For example if we update a list of 100 items 1000 times, this creates more > than 100,000 tombstones and exceeds the default tombstone_failure_threshold. -- This message was sent by Atlassian JIRA (v6.3.4#6332)