|
|
|
If a reboot (or cpstop followed by cpstart) is performed on a cluster member while the cluster is under severe load, the member may fail to start correctly. The starting member will attempt to perform a full sync with the existing active member(s) and may in the process use up all its resources and available memory. This can lead to unexpected behavior.
To overcome this problem, define the maximum amount of memory that the member may use when starting up for synchronizing its connections with the active member. By default this amount is not limited. Estimate the amount of memory required as follows:
|
New connections/second |
|||
Number of open |
100 |
1000 |
5000 |
10,000 |
1000 |
1.1 |
6.9 |
|
|
10000 |
11 |
69 |
329 |
|
20000 |
21 |
138 |
657 |
1305 |
50000 |
53 |
345 |
1642 |
3264 |
For example, if the cluster holds 10,000 connections, and the connection rate is 1000 connections/sec you will need 69 MB for full sync.
Define the maximum amount of memory using the Security Gateway global parameter: fw_sync_max_saved_buf_mem.
The units are in megabytes. For details, see Advanced Cluster Configuration.
