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

Estimated TS drop-time histogram updated with Cell.NO_DELETION_TIME

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 3.0.11, 3.10, 4.0, 4.0-alpha1
    • Component/s: None
    • Labels:
      None
    • Severity:
      Normal

      Description

      Starting with 3.0, MetadataCollector.updateLocalDeletionTime(int newLocalDeletionTime) will be called with cell.localDeletionTime() in order to update the min/max deletion times as well as the estimatedTombstoneDropTime histogram. Currently this also happens for Cell.NO_DELETION_TIME (Integer.MAX_VALUE), which causes the histogram to be called for every regular cell.

      This can be easily verified by using sstablemetadata on any sstable. You should be able to find a very high value for 2147483647 in the "Estimated tombstone drop times" section.

      At this point, I don't think this is causing serious harm, but could be a performance issue (see linked ticket). Calculated droppable TS times should not be affected.

        Attachments

        1. 13040-3.0.patch
          2 kB
          Stefan Podkowinski

          Issue Links

            Activity

              People

              • Assignee:
                spod Stefan Podkowinski
                Reporter:
                spod Stefan Podkowinski
                Authors:
                Stefan Podkowinski
                Reviewers:
                Jason Brown
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: