Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CNDB-9104: Port over chunk cache improvements from DSE #1495
base: main
Are you sure you want to change the base?
CNDB-9104: Port over chunk cache improvements from DSE #1495
Changes from 20 commits
3968200
1ad3ac4
cfa0842
0f84fc2
31a5fda
6aa0130
1a15fa5
c4f14ee
307aa7f
be317b2
1313839
36be7e5
9190348
d4e230e
d5a22c8
fa2551f
89817b4
c0c4716
7ab70b0
2539b18
c01dbb7
5262c59
7f0d6ba
6686f6d
462fb34
d755d32
9fc879e
09199b3
3f08d7f
ba1232f
226bc15
743e53a
1bbc990
dac75ad
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd argue that not using the local
chunkCache
here is a regression, for 2 reasons:chunkCache.get() == ChunkCache.instance
. But currently in CNDB we sometimes use a different chunk cache instance for some filse, where this would be incorrect. Admittedly, the benefits of that separate instance are debatable, but it is used currently.FileHandle
is meant to use it, which is technically not guarantee. In theory, nothing quite forbid the same file from being opened in one place with use of the chunk cache but also in another where it doesn't. Given thatFileHandle
is used a lot, including in CNDB, I think it's better not to rely on this never being a legit use case.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This whole code is now dropped, because it is obliterating the effect of early open. Whatever solution we choose, it cannot be done during handle cleanup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in CNDB we use the ChunkCache also for SAI, should we add some specifc handling ?
cc @pcmanus
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to the file handle builder to use the supplied cache instance.