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

Fix CollationController#collectTimeOrderedData() mostRecentRowTombstone tracking

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 2.0.9, 2.1 rc3
    • Component/s: None
    • Labels:
      None
    • Severity:
      Low

      Description

      As of now, collectTimeOrderedData() will try to read from at least one sstable, even if the memtable has a row tombstone with a higher timestamp than any max timestamp in the sstable. If we initiate mostRecentRowTombstone with the value from the memtables and not Long.MIN_VALUE, reading from the sstables can be avoided entirely in this scenario.

      Current tracking is also broken b/c we update mostRecentRowTombstone value with the one read from the last sstable, unconditionally, even if it's a lesser tombstone than we used to have tracked.

        Attachments

        1. 7394.txt
          2 kB
          Aleksey Yeschenko

          Issue Links

            Activity

              People

              • Assignee:
                aleksey Aleksey Yeschenko
                Reporter:
                aleksey Aleksey Yeschenko
                Authors:
                Aleksey Yeschenko
                Reviewers:
                Jonathan Ellis
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: