Add soft TTL to Query Cache entries #4086
Merged
Conversation
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
javsanpar
force-pushed
the
v2.x-1486
branch
2 times, most recently
from
72f6441
to
882e142
Compare
When Query Cache entries reach the soft ttl, the next query hit the backend and refresh the entry. While the refresh happens, other queries keeps getting the "old" Query Cache entry. Soft ttl is a percentage of the cache ttl and is defined by a global variable for all the entries. If the value is 0, soft ttl is disabled and no used.
javsanpar
force-pushed
the
v2.x-1486
branch
3 times, most recently
from
e7c8f69
to
e8b1897
Compare
|
@renecannao @javsanpar is there a way with which one can decide if the current call itself be served from the cache and it just initiates the refresh call. Like why to even make the current call wait for the actual db call. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When Query Cache entries reach the soft ttl, the next query hit the
backend and refresh the entry. While the refresh happens, other queries
keeps getting the "old" Query Cache entry.
Soft ttl is a percentage of the cache ttl and is defined by a global
variable for all the entries. If the value is 0, soft ttl is disabled
and no used.
Related to issue #1486