Skip to content

Commit 962121e

Browse files
Merge pull request #312 from shapeblue/stickinessPolicyDetails
Added details to the stickiness policy under load balancing
2 parents 70fdf0c + 7d95054 commit 962121e

File tree

1 file changed

+55
-3
lines changed

1 file changed

+55
-3
lines changed

source/adminguide/networking/external_firewalls_and_load_balancers.rst

Lines changed: 55 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -348,10 +348,62 @@ automatically generated. A variety of options are provided to control
348348
the exact behavior of cookies, such as how they are generated and
349349
whether they are cached.
350350

351-
For the most up to date list of available stickiness methods, see the
352-
CloudStack UI or call listNetworks and check the
353-
SupportedStickinessMethods capability.
351+
There are three stickiness methods that are supported explained with the possible options to configure as below,
354352

353+
1. Lbcookie: In this method, cookie is created by the load balancer and sent to the client.
354+
The client sends this cookie back with every subsequent request, and the load balancer uses the
355+
cookie information to determine which backend server to route the request to.
356+
357+
Following are the options available to configure,
358+
359+
- Cookie name: This is the name of the cookie that the load balancer will create and send to the client.
360+
361+
- Mode: This option determines how the load balancer should handle the cookie (default value is insert).
362+
The available options are:
363+
364+
a. Insert: The load balancer will insert the cookie into the client's request.
365+
b. Rewrite: The load balancer will rewrite the cookie in the client's request if it already exists.
366+
c. Prefix: The load balancer will prefix the cookie name with a specified prefix.
367+
d. Indirect: The load balancer will insert an indirect cookie, which contains a reference to the actual cookie value.
368+
369+
- No cache: This option specifies whether the cookie should be cached by the client's browser.
370+
If this option is enabled, the client's browser will not cache the cookie.
371+
372+
- Indirect: If this is provided, then the cookie value will contain a reference to the actual value, which will be stored on the load balancer.
373+
374+
- Post only: This option specifies whether the cookie should be sent only with POST requests.
375+
376+
- Domain: This option specifies the domain for which the cookie is valid. You can specify a domain name or IP address.
377+
378+
2. Appcookie: In this method, the application running on the backend servers creates a cookie and
379+
sends it to the client. The client sends this cookie back with every subsequent request, and the
380+
load balancer uses the cookie information to determine which backend server to route the request to.
381+
382+
Following are the options available to configure,
383+
384+
- Cookie name and mode are same as above
385+
386+
- Length: This option specifies the length of the cookie value (default value is 52).
387+
388+
- Hold time: This option specifies the length of time that the cookie should be held (default value is 3hours).
389+
The cookie will be held for this amount of time, after which it will expire.
390+
391+
- Request learn: This option specifies whether the load balancer should learn the cookie value from the first request that it receives.
392+
393+
- Prefix: This option specifies a prefix to be added to the cookie value.
394+
395+
3. Source-based: In this method, the load balancer uses the source IP address of the client
396+
to determine which backend server to route the request to. The load balancer maintains a mapping of
397+
client IP addresses to backend servers and uses this mapping to ensure that subsequent requests from
398+
the same client are always routed to the same backend server.
399+
400+
- Table size: This option specifies the maximum number of entries (default 200k) that can be stored in the source-based stickiness table.
401+
The table stores mappings between client IP addresses and backend servers.
402+
403+
- Expires: This option specifies the length of time (default 30m) that a mapping between a client IP address and a backend server
404+
should be kept in the stickiness table. After this time has elapsed, the mapping will expire and be removed from the table.
405+
406+
4. None: If None is selected after a sticky policy is already configured then it will be removed.
355407

356408
Load Balancer Configurations
357409
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0 commit comments

Comments
 (0)