Setting Service Load Timeout 

Use

Use the procedure to change the maximum time for which all services on a cluster node have to be started.

If there are still services that have not started after this timeout, the behavior of the Service Manager depends on the value of the ServiceTimeoutAction property. The possible values are:

●      wait

The Service Manager blocks the startup operation until all services are started and performs thread dumps every 5 minutes.

●      halt

The Service Manager calls critical shutdown and restarts the server process.

●      ignore

The Service Manager assumes that all services are started and the system continues with the other startup processes.

The default value depends on the template. We recommend for production systems to set the value to halt, and for development and test purposes to set the value to wait.

In case of problems during cluster node startup, for example, if there are large clusters, check the log files for services that have timed out during startup. If there are such cases, we recommend that you increase the default timeout from 7 to up to 20 minutes.

Procedure

...

       1.      Start the Config Tool.

       2.      Choose cluster-data à template à instance - <n> à managers à ServiceManager.

       3.      From the list of properties, select LoadTimeout.

       4.      In the Custom value field, set the required timeout in minutes.

       5.      To apply the new value, choose Set.

       6.      To save the changes, choose  Apply changes.

       7.      For the changes to take effect, restart the cluster.

You can use the procedure analogically for setting the value of ServiceTimeoutAction.