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

Tombstone/Partition not purged after gc_grace_seconds

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Normal

    Description

      During a tombstone purge (reducing gc_grace_seconds to zero and running `nodetool garbagecollect`), I noticed that when doing a dump of the SSTable, sometimes, there are a few partitions that do not get completely purged, even with gc_grace_seconds set to zero. I was able to replicate this in a small test dataset, from which I have attached the SSTable files and the schema to this ticket so that you can verify this as well.
      Doing a dump of the mc-51-big-Data.db file, you'll notice the following partition:

      {
      "partition" : {
      "key" : [ "96" ],
      "position" : 285,
      "deletion_info" :

      { "marked_deleted" : "2019-03-14T21:31:55.244490Z", "local_delete_time" : "2019-03-14T21:31:55Z" }

      },
      "rows" : [ ]
      },

      As you can see, the rows were removed correctly by the garbagecollect, but the partition record, continues there, and never goes away.
      From the client side, no data is returned, so it's good there. But regardless of that, this partition should not be present in the SSTable file.

      Attachments

        1. schema.cql
          0.9 kB
          Pedro Gordo
        2. sstables.tar
          30 kB
          Pedro Gordo

        Activity

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

          People

            Unassigned Unassigned Assign to me
            pedro_gordo Pedro Gordo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment