You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If compactor use the same opendal backend (and cache directory) as datanode, it may pollute the cache in opendal backend especially compaction legacy sst files.
Implementation challenges
Separate opendal backend in compactor and datanode. Backend in compactor should only read file cache but not write to it.
The text was updated successfully, but these errors were encountered:
Due to the pending optimization on access layer cache, we can now remove the cache layer during compaction. Theoretically, this change won't affect compaction performance, in that most reads in compaction do not retrieve repeated ranges.
What type of enhancement is this?
Performance
What does the enhancement do?
If compactor use the same opendal backend (and cache directory) as datanode, it may pollute the cache in opendal backend especially compaction legacy sst files.
Implementation challenges
Separate opendal backend in compactor and datanode. Backend in compactor should only read file cache but not write to it.
The text was updated successfully, but these errors were encountered: