[OpenShift Container Platform][IBM MQ Advanced]

Advanced tuning for Native HA

Advanced settings for tuning timings and intervals. There should be no need to use these settings unless the defaults are known not to match your system's requirements.

The basic options for configuring Native HA are handled using the QueueManager API, which the IBM® MQ Operator uses to configure the underlying queue manager INI files for you. There are some more advanced options that are only configurable using an INI file, under the NativeHALocalInstance stanza. See also Example: Supplying MQSC and INI files for more information on how to configure an INI file.

HeartbeatInterval
The heartbeat interval defines how often in milliseconds an active instance of a Native HA queue manager sends a network heartbeat. The valid range of the heartbeat interval value is 500 (0.5 seconds) to 60000 (1 minute), a value outside of this range causes the queue manager to fail to start. If this attribute is omitted, a default value of 5000 (5 seconds) is used. Each instance must use the same heartbeat interval.
HeartbeatTimeout
The heartbeat timeout defines how long a replica instance of a Native HA queue manager waits before it decides that the active instance is unresponsive. The valid range of the heartbeat interval timeout value is 500 (0.5 seconds) to 120000 (2 minutes). The value of the heartbeat timeout must be greater than or equal to the heartbeat interval.

An invalid value causes the queue manager to fail to start. If this attribute is omitted a replica waits for 2 x HeartbeatInterval before starting the process to elect a new active instance. Each instance must use the same heartbeat timeout.

RetryInterval
The retry interval defines how often in milliseconds a Native HA queue manager should retry a failed replication link. The valid range of the retry interval is 500 (0.5 seconds) to 120000 (2 minutes). If this attribute is omitted a replica waits for 2 x HeartbeatInterval before retrying a failed replication link.