feat: new 'db_resurrect_ttl' configuration property + resilient cache callbacks #3579
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.
This new version adds support for
resurrect_ttl
, which resurrectsstale values when the callback fails on soft errors.
https://github.com/thibaultcha/lua-resty-mlcache/blob/master/CHANGELOG.md#220
Documentation for its behaviour can be read in the description test
included in kong.conf.default.
In order for the resurrection of stale cached values to occur when
callback I/O fails (see c932dc6), we have to return soft errors from our
callbacks, and not throw them via error().
Additionally, we rely on the modern behavior of mlcache with regards to
the caching of cache misses - returning
nil
is cached my mlcache.