You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/features/proxy/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The proxy configuration organizes backends into one or more named groups called
34
34
35
35
When the proxy receives a request to read or write cache data under a given key, the proxy uses various criteria to select one of its pools. It then forwards the cache request to a backend within that pool. For more information, see [Routing criteria](#routing).
36
36
37
-
Once it has selected a pool to route a request to, the proxy chooses a single backend within the pool based on a consistent hash of the request key. In this way, a given key is always handled by the same backend within a given pool. You can fine-tune the specifics of this hashing behavior, as well as other pool-specific settings, when [configuring your pools]({{<proxy_base_path>}}configure#pools).
37
+
Once it has selected a pool to route a request to, the proxy chooses a single backend within the pool based on a consistent hash of the request key. In this way, a given key is always handled by the same backend within a given pool, for as long as that backend exists within that pool. You can fine-tune the specifics of this hashing behavior, as well as other pool-specific settings, when [configuring your pools]({{<proxy_base_path>}}configure#pools).
0 commit comments