cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12208) Estimated droppable tombstones given by sstablemetadata counts tombstones that aren't actually "droppable"
Date Thu, 14 Jul 2016 23:01:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams updated CASSANDRA-12208:
-----------------------------------------
    Assignee: Marcus Eriksson

> Estimated droppable tombstones given by sstablemetadata counts tombstones that aren't
actually "droppable"
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12208
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12208
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Thanh
>            Assignee: Marcus Eriksson
>            Priority: Minor
>
> => "Estimated droppable tombstones" given by *sstablemetadata* counts tombstones that
aren't actually "droppable"
> To be clear, the "Estimated droppable tombstones" calculation counts tombstones that
have not yet passed gc_grace_seconds as droppable tombstones, which is unexpected, since such
tombstones aren't droppable.
> To observe the problem:
> Create a table using the default gc_grace_seconds (default gc_grace_seconds is 86400
is 1 day).
> Populate the table with a couple of records.
> Do a delete.
> Do a "nodetool flush" to flush the memtable to disk.
> Do an "sstablemetadata <sstable>" to get the metadata of the sstable you just created
by doing the flush, and observe that the Estimated droppable tombstones is greater than 0.0
(actual value depends on the total number inserts/updates/deletes that you did before triggered
the flush)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message