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

Legacy deserializer can create empty range tombstones

    XMLWordPrintableJSON

    Details

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

      Description

      Range tombstones in the 2.x file format is a bit far-westy so you can actually get sequences of range tombstones like [1, 4]@3 [1, 10]@5. But the current legacy deserializer doesn't handle this correctly. On the first range, it will generate a INCL_START(1)@3 open marker, but upon seeing the next tombstone it will decide to close the previously opened range and re-open with deletion time 5, so will generate EXCL_END_INCL_START(1)@3-5. That result in the first range being empty, which break future assertions in the code.

        Attachments

          Activity

            People

            • Assignee:
              slebresne Sylvain Lebresne
              Reporter:
              slebresne Sylvain Lebresne
              Authors:
              Sylvain Lebresne
              Reviewers:
              Branimir Lambov
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: