Determining whether the Primary settings take precedence over the Secondary settings
Some parameters must be the same for both the Primary and Secondary servers. If you do not set the parameters to same values, you might expect that each server uses the value that is defined in solid.ini file of the server. However, this is not necessarily the case.
Even for some parameters that control the behavior of the Secondary, such as 2SafeAckPolicy, the value on the Primary is the value that determines the behavior. The principle is that all safeness and durability parameters are controlled at the Primary. For example, the Primary reads its value of 2SafeAckPolicy and sends that value to the Secondary to use. The value stored in the Secondary’s solid.ini file is used only if the Secondary becomes the Primary.
The values set at the Primary take precedence over the values set at the Secondary for the following parameters:
▪HotStandby.SafenessLevel
▪HotStandby.2SafeAckPolicy
▪Logging.DurabilityLevel
▪HotStandby.NetcopyRpcTimeout
When the command hsb connect is issued, the following Primary parameters take precedence: