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

Single partition reads can read more SSTables than required

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

Details

    Description

      For some scenarios involving row deletions, range deletions or static columns, the logic of SinglePartitionReadCommand.queryMemtableAndSSTablesInTimestampOrder might trigger more SSTables reads that expected.

      For row deletions and range deletions the reasons is that the logic do not take them into account. Once we hit a deleted row (caused by a row deletion or a range deletion) with a timestamp higher than the one of the next SStable we know that we can stop reading more SSTables.

      For static columns the problems seems to have been introduced by the changes in CASSANDRA-16671.

      Attachments

        Activity

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

          People

            blerer Benjamin Lerer Assign to me
            blerer Benjamin Lerer
            Benjamin Lerer
            Caleb Rackliffe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h
                1h

                Issue deployment