Configuration database failover timeout

The configuration database failover timeout setting specifies how many seconds a secondary management server should wait before taking over as the primary when the primary server cannot be reached.

About this task

Increasing the timeout value allows for more time to reestablish communication, reducing the possibility of the configuration becoming inconsistent with more than one server becoming primary. Increasing the failover timeout period may be necessary if the network connection between the management servers is not reliable or is prone to delays.
Note: Note: Change this advanced setting with caution and only if necessary.
For more information, see Dissociation and your cloud and Define the main site in your API Connect cloud.

Increasing the failover timeout reduces the high availability of the management servers in the cloud. (During the failover timeout period, the secondary management servers is not able to process updates if they cannot communicate with the primary server).

Procedure

To change the configuration database failover timeout setting, complete the following steps. The default failover timeout is set to 60 seconds. The timeout cannot be set to lower than 10 seconds. Typically, you would not set this failover timeout to higher than 300 seconds (5 minutes).

  1. In the Cloud Manager, click Settings.
  2. On the left hand side of the Settings page, click Advanced.
  3. For the Configure Database Failover Timeout setting, enter the new failover timeout setting in seconds.
  4. Click Save.

Results

The timeout setting is changed.