Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
Currently, compactions invalidate key cache entries that pointed to the SSTables that were compacted. This results in a sudden increase in the number of seeks necessary for reads immediately after compaction. When writing out a new SSTable after a compaction, it seems like it should be possible to store a list of keys that are currently cached but would be invalidated along with their new position in the new SSTable. Matt Dennis also seems to think this would be relatively easy to do.