nginx: add proxy_cache_lock, so we wait one request to populate cache if there is one ongoing for that cache-key #3604
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.
Description
Add lock in nginx level that only one request gets in if cache is miss and others wait that one request at max of 10s to get response and populate cache, which is served to other requests hitting the same cache-key.
Alternative approach to #2809
What type of Pull Request is this?
Does this PR change settings or dependencies, or break something?
Details of breaking or configuration changes (if any of above checked)
Nginx caching rules are changed, to prevent huge amount of identical requests to cause load on instance
Documentation
Tests