Use the information in this section to plan the installation and configuration of any data service. The information in this section encourages you to think about the impact your decisions have on the installation and configuration of a data service. For specific considerations for a data service, see the documentation for the data service.
Retries within the I/O subsystem during disk failures might cause applications whose data services are disk intensive to experience delays. Disk-intensive data services are I/O intensive and have a large number of disks configured in the cluster. An I/O subsystem might require several minutes to retry and recover from a disk failure. This delay can cause Oracle Solaris Cluster to fail over the application to another node, even though the disk might have eventually recovered on its own.
To avoid failover during these instances, consider increasing the default probe timeout of the data service. Also consider setting the Timeout_threshold property to notify you when a resource is nearing a timeout limit. Use of the Timeout_threshold property can help you avoid a false failover. If you need more information or help with increasing data service timeouts, contact your local support engineer.
For better performance, install and configure your data service on the cluster nodes with direct connection to the storage.
Client applications that run on cluster nodes should not map to logical IP addresses of an HA data service. After a failover, these logical IP addresses might no longer exist, leaving the client without a connection.