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

Estimated TS drop-time histogram updated with Cell.NO_DELETION_TIME

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 3.0.11, 3.10, 4.0-alpha1, 4.0
    • None
    • None
    • 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

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            spod Stefan Podkowinski Assign to me
            spod Stefan Podkowinski
            Stefan Podkowinski
            Jason Brown
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment