Skip to content
Search to learn about InterSystems products and solutions, career opportunities, and more.

Advisory: Mirroring Default QoS Value Considerations

April 28, 2015 – Advisory: Mirroring Default QoS Value Considerations

InterSystems has determined that the default value of the mirroring Quality of Service Timeout (QoS) setting is too small for some environments.  This can result in undesired mirror failovers and/or unnecessary alerts.

This advisory applies to all platforms.  Although the issue exists with any version of Caché, Ensemble or HealthShare that supports mirroring, this advisory is of particular note to deployments using version 2015.1 with the arbiter.

The Quality of Service Timeout (QoS timeout) setting affects failover member and arbiter behavior by defining the range of time, in milliseconds, that a mirror member waits for a response from another mirror member before taking action. The QoS timeout itself sets the maximum waiting time, while the minimum is one-half of that. A larger QoS timeout allows the mirror to tolerate a longer period of unresponsiveness from the network or a host without treating it as an outage; decreasing the QoS allows the mirror to respond to outages more quickly.

InterSystems has observed that virtualized hosts, in particular, often become entirely unresponsive for periods that exceed the default QoS value when operations such as backup or guest migration occur.  Typically, deployments on physical (non-virtualized) hosts with a dedicated local network can operate within the default QoS value continually.

The default QoS timeout is 2 seconds (2000 ms).  In future versions, the default QoS timeout will be 8 seconds (8000 ms) to allow for several seconds of intermittent unresponsiveness that may occur on some hardware configurations.

InterSystems recommends reviewing your hardware configuration and the effects of any operations regularly performed on the virtualization hosts to determine a reasonable setting for QoS.  In deciding whether to increase the QoS timeout, the potential of an undesired failover should be weighed against a slower response time during actual outages.  The timeout can be changed via the System Management Portal ‘Edit Mirror’ page, or via the ^MIRROR utility.  If you have any questions regarding this advisory, please contact InterSystems’ Worldwide Response Center.

Latest Alerts & Advisories

Aug 15, 2024
InterSystems has corrected a defect that can cause database corruption or errors with multi-volume databases under extremely rare circumstances. Only databases that have been truncated are at risk.
Jul 25, 2024
There are four alerts in the HS2024-03 Alert Communication. A summary of each alert is shown below. Details for each alert are contained in the linked document.
Jun 24, 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
May 30, 2024
Beginning with the release of InterSystems IRIS® data platform 2022.3, InterSystems corrected the license enforcement mechanism to include REST and SOAP requests. Due to this change, environments with non-core-based licenses that use REST or SOAP may experience greater license utilization after upgrading. To determine if this advisory applies to your InterSystems license, follow the instructions in the FAQ linked below.
May 01, 2024
InterSystems has corrected an issue that can cause a small number of SQL queries to return incorrect results. See below for the specifics on impacted queries.
Apr 09, 2024
InterSystems has encountered a defect that causes some upgrades of HealthShare® Health Connect to fail. This only affects instances that are not licensed for the use of FHIR® and that have interoperability-enabled namespaces. Under these conditions, the upgrade fails with an error.
Mar 19, 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
Feb 27, 2024
There is 1 alert in the HealthShare HS2024-limited Alert communication. An alert summary for the issue is shown is in the table below. Details for the alert are contained in the attached document: HS2024 Limited Communication.
Feb 01, 2024
There are 2 alerts in the HealthShare HS2024-02 Alert communication. An alert summary for each issue is shown is in the table below. Details for each alert are contained in the attached document: HS2024-02-Communication.