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

Fix counting of tombstones towards TombstoneOverwhelmingException

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.0.15, 2.1.6
    • Component/s: None
    • Labels:
      None
    • Severity:
      Normal

      Description

      CASSANDRA-6042 introduced warning on too many tombstones scanned, then CASSANDRA-6117 introduced a hard TombstoneOverwhelmingException condition.

      However, at least SliceQuerFilter.collectReducedColumn() seems to have the logic wrong. Cells that are covered by a range tombstone or a partition high level deletion, still count towards ColumnCounter's ignored register.

      Thus it's possible to have an otherwise healthy (though large) dropped partition read cause an exception that shouldn't be there.

      The only things that should count towards the exception are cell tombstones and range tombstones (CASSANDRA-8527), but never ever live cells shadowed by any kind of tombstone.

        Attachments

        1. 9299-2.0.txt
          12 kB
          Aleksey Yeschenko
        2. 9299-2.1.txt
          14 kB
          Aleksey Yeschenko
        3. 9299-trunk.txt
          18 kB
          Aleksey Yeschenko

        Issue Links

          Activity

            People

            • Assignee:
              aleksey Aleksey Yeschenko Assign to me
              Reporter:
              aleksey Aleksey Yeschenko
              Authors:
              Aleksey Yeschenko
              Reviewers:
              Tom Hobbs

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment