-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Use reader wrapper in ReadOnlyEngine #75724
Use reader wrapper in ReadOnlyEngine #75724
Conversation
Pinging @elastic/es-distributed (Team:Distributed) |
- match: { nodes.$node_id.shared_cache.bytes_written: "0b" } | ||
- match: { nodes.$node_id.shared_cache.bytes_written_in_bytes: 0 } | ||
- match: { nodes.$node_id.shared_cache.evictions: 0 } | ||
- gte: { nodes.$node_id.shared_cache.reads: 0 } |
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 is an interesting side-effect here because we now actually start using the cache.
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.
LGTM
Ensures the reader wrapper is always used in ReadOnlyEngine.
Ensures the reader wrapper is always used in ReadOnlyEngine.
Ensures the reader wrapper is always used in ReadOnlyEngine.
Thanks for fixing this Yannick! |
Ensures the reader wrapper is always used in ReadOnlyEngine. To test this PR, I enabled security on the searchable snapshot REST tests.