Repository navigation
docs(rate-limiting): document sync_rate realtime fallback for short periods - #7400
Draft
rajtherengan wants to merge 1 commit into
Draft
rajtherengan wants to merge 1 commit into
rajtherengan wants to merge 1 commit into
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
Contributor
|
Thanks for your submission! I'm marking this PR as draft for now so that it doesn't get merged before the related engineering side PR. |
This file contains hidden or 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
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.
Documents the behavior change in Kong/kong#15037 (related issue: Kong/kong#15018): with the
redispolicy, periods not longer thansync_rateare now synced to Redis on every request, and a warning is logged.Opening as a draft until the code PR is merged. The
3.Xplaceholder needs the release that ships the fix; once known, it could become{% new_in <version> %}on the heading instead.