High Availability Properties
This section describes the different high availability properties that you can use in the STR. For further information about high availability, see High Availability Setup.
All Pico Types
These properties are applicable to all pico types.
Property | Description | SOC 1 | Category | Reason |
|---|---|---|---|---|
mz.ha.enabled | Default value: false This property enables the HA Monitoring Server on a pico instance. | Yes | Availability | Enables high-availability monitoring; impacts failover/uptime behavior. |
mz.ha.log_file | Default value: This property determines the directory where the HA Monitor Server will store log files. The log file contains the property assignments, that is, counter limits as well as debug and statistics information. The default setting is an empty value, meaning that the HA logging is disabled. | Yes | Integrity | Controls capture/location of HA monitoring logs; disabled or misdirected logging reduces completeness of evidence. |
mz.ha.host | Default value: This property determines the address of the interface that the HA Monitor Server will bind to. The HA Client typically runs on the same host as the HA Monitor server that it connects to. | Yes | Availability | Sets the bind address for the HA monitor; misconfiguration can prevent HA monitoring and impact failover/uptime. |
mz.ha.port | Default value: This property determines the port that the server will bind to. This parameter must be set if an HA monitor server is used. | Yes | Availability | Sets the HA monitor’s listening port; missing/incorrect value can break monitoring and affect failover/uptime. |
Execution Contexts
These properties are applicable to ECs.
If multiple properties are specified, the ping returns FAILED if any of the properties do not comply with their respective threshold.
Property | Description | SOC 1 | Category | Reason |
|---|---|---|---|---|
mz.ha.interval | Default value: This property defines the time interval, in seconds, for the counters specified below, i.e. mz.ha.min_number_of_transactions, mz.ha.max_aborts. mz.ha.min_activations, mz.ha.min_activations_for_aborts, and mz.ha.min_consumes. The time interval must be at least 40 seconds. If a lower number is stated, the used value will be 40 seconds. | Yes | Availability | Defines monitoring interval for HA counters; improper value can impair detection of issues and affect uptime. |
mz.ha.min_activations | Default value: This property defines the minimum number of workflow activations required before the number of aborts are counted. The default value "-1" means that the counter is disabled. | Yes | Availability | Sets threshold for counting aborts; misconfiguration can impair monitoring sensitivity and affect uptime. |
mz.ha.min_activations_for_aborts | Default value: This property must be used in combination with the mz.ha.max_aborts property to get a notion of the maximum number of aborts allowed within the mz.ha.interval. The default value "-1" means that the counter is disabled. | Yes | Availability | Works with |
mz.ha.min_consumes | Default value: This property defines the minimum number of consumed UDRs required within the mz.ha.interval. This property is mainly used for realtime workflows. The default value "-1" means that the counter is disabled. | Yes | Availability | Sets minimum consume rate; improper threshold weakens detection of stalled realtime processing. |
mz.ha.min_number_of_transactions | Default value: Defines the minimum number of closed transactions required within the mz.ha.interval. Used for batch workflows on an EC, since realtime workflows do not generate transactions. The default value "-1" means that the counter is disabled. | Yes | Availability | Sets minimum closed transactions; misconfiguration can mask batch slowdowns/outages. |
mz.ha.max_aborts | Default value: This property defines the maximum number of aborts allowed within the mz.ha.interval. The default value "-1" means that the counter is disabled. | Yes | Availability | Caps allowed aborts per interval; loose/tight settings can hide instability or cause false alarms impacting uptime. |