Skip to content

Commit 75c3360

Browse files
jmacdotorgdormando
authored andcommitted
Add more description about how pools work to the overview.
1 parent aeb6f6d commit 75c3360

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/features/proxy/_index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,8 @@ Setting up a backend doesn't require any special Memcached configuration. A back
3333
The proxy configuration organizes backends into one or more named groups called <em>pools</em>. Each pool contains one or more backends.
3434

3535
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+
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).
3638
</dd>
3739

3840
<dt>Set</dt>

0 commit comments

Comments
 (0)