Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-13024

Droppable Tombstone Ratio Calculation

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Local/Compaction
    • Labels:
      None
    • Severity:
      Normal

      Description

      Whenever no sstables can be compacted in a standard way, we currently try to compact sstables that would make worthwhile candidates by evaluation sstable.getEstimatedDroppableTombstoneRatio(gcBefore) <= tombstoneThreshold. You can find out more on how this is supposed to work and the various settings options by reading "About Deletes and Tombstones in Cassandra" by Alain RODRIGUEZ.

      The bad news is that currently the ratio value will vary to a great degree depending on the data model and type of deletes, as the ratio will be created based on the number of tombstones and number of columns. Any kind of tombstone will be counted here, no matter if on column or partition level, which will give you very different ratios based on the number of columns in your table and how you delete the data.

      Considering a 0.20 default threshold for finding sstables with enough droppable tombstones, it only takes 3 columns in your table to never hit the threshold at all when using partition tombstones.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                spod Stefan Podkowinski
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: