Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove broken "defragment-on-read" optimization
The read path for names queries has had a "defragment-on-read" optimization for a while whereby if too many sstables are hit by the read, the result is written back into memtable, in the hope that later reads will only read that newly written data in a single sstable (or at least fewer). The principle of that optimisation does not work however as data is written back with the same timestamp as it originally has and that means future reads cannot know to skip older sstables (at least with the metadata we currently store). As such, this optimisation never saved anything and in fact added load. The patch removes that broken code. Patch by Sylvain Lebresne, reviewed by Aleksey Yeschenko for CASSANDRA-15432
- Loading branch information
Showing
5 changed files
with
1 addition
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters