Page History
...
- The Cluster Service is used to operate a passive cluster of JOC Cockpit instances and to perform fail-over and switch-over operations between cluster members.
- All other JS7 - Services depend on the Cluster Service in order to be started start them for the active JOC Cockpit instance.
...
Location
- The "Settings" menu is available can be accessed in the JOC Cockpit GUI.
Configuration Items
| Section | Setting | Default | Required | Purpose |
|---|---|---|---|---|
| cluster | heart_beat_exceeded_interval | 60 | no | The duration in seconds to signal that heartbeats from an active cluster member to the database did not arrive in time and that fail-over to the next passive cluster member should occur. |
polling_interval | 30 | no | The interval in seconds between sending heartbeats to the database. | |
polling_wait_interval_on_error | 2 | no | The interval in seconds to continue polling after an error has occurred, e.g. due to transactional concurrency etc. | |
switch_member_wait_counter_on_success | 10 | no | The number of retries to wait for the answer from the last active cluster member after its deactivation/activation. | |
switch_member_wait_interval_on_success | 5 | no | The maximum number of seconds to wait for a cluster member to become active. max wait time = switch_member_wait_counter_on_success * switch_member_wait_interval_on_success + execution time | |
switch_member_wait_counter_on_error | 10 | no | The maximum number of retries in case of errors, e.g. due to transactional concurrency etc., to switch the cluster to a different member. | |
switch_member_wait_interval_on_error | 2 | no | The maximum number of seconds to wait for a cluster member to become active after an error. max wait time = switch_member_wait_counter_on_error*switchMemberWaitIntervalOnError+ execution time | |
current_is_cluster_member | true | no | Enable cluster to switch to this instance. |
...
Overview
Content Tools