|
|
|
When policy is installed on a Cluster, the Cluster Members undertake a negotiation process to make sure all of them have received the same policy before they actually apply it. This negotiation process has a timeout mechanism, which makes sure a Cluster Member does not wait indefinitely for responses from other Cluster Members, which is useful in cases when another Cluster Member goes down when policy is being installed (for example).
In configurations, on which policy installation takes a long time (usually caused by a policy with a large number of rules), a cluster with more than two members, and slow members, this timeout mechanism may expire prematurely.
It is possible to tune the timeout by setting the following kernel parameter:
fwha_policy_update_timeout_factor
The default value is 1, which should be sufficient for most configurations. For configurations where the situation described above occurs, setting this parameter to 2 should be sufficient. Do NOT set this parameter to a value larger than 3.
