JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.0
search filter icon
search icon

Document Information


1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

Introduction to Heartbeats

Creating a Heartbeat

How to Create a Heartbeat

Creating a Heartbeat Plug-in

How to Create Heartbeat Plug-in

Modifying a Heartbeat Plug-in Property

How to Modify the Properties of a Heartbeat Plug-in

Deleting Heartbeats and Heartbeat Plug-ins

How to Delete a Heartbeat

How to Delete a Plug-in From a Heartbeat

Displaying Heartbeat Configuration Information

How to Display Heartbeat Configuration Information

Tuning the Heartbeat Properties

How to Modify the Heartbeat Properties

Creating a Heartbeat That Uses a Custom Heartbeat Plug-in

Creating a Custom Heartbeat Plug-in

How to Add a Custom Heartbeat Plug-in to an Existing Default Heartbeat

How to Create a Custom Heartbeat Plug-in and Add It to a Custom Heartbeat

Configuring Heartbeat-Loss Notification

Configuring the Heartbeat-Loss Notification Properties

Creating an Action Shell Script for Heartbeat-Loss

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Error Return Codes for Script-Based Plug-Ins


Tuning the Heartbeat Properties

Default heartbeats are created as part of partnership creation. If you use a custom heartbeat, the custom heartbeat should be created before you create a partnership. You can modify the properties of the default and custom heartbeats by using the geohb set-prop command. For more information about this command, refer to the geohb(1M) man page.

Note - Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Oracle specialist for assistance if your system requires the use of custom heartbeats.

If you modify the default value of the Query_interval property, ensure that the interval is sufficiently long. An interval that is too short causes a timeout and heartbeat-loss event before the logical hostname resource is available. This failover should result in no more than two unanswered heartbeat requests. Setting a default query_interval value of 120 seconds with the default heartbeat.retries parameter of 3 enables the peer cluster to be unresponsive for 6 minutes (120 * 3 ) without having a false failure declared.

The heartbeat.retries parameter is specified in the com.sun.cluster.agent.geocontrol.xml file.

If you adjust the delay setting of the Query_interval property, ensure that the following condition is met:

Query_interval > worst-case logical-host failover time / 2

You must empirically determine the logical-host failover time for the cluster in question.

The following must be true to avoid false failures:

Query_interval > worst-case logical-host failover time / 3

You should not change the heartbeat.retries value. If you want to change the default value of the heartbeat.retries property, contact an Oracle service representative.

How to Modify the Heartbeat Properties

  1. Log in to a cluster node.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Geographic Edition Software and RBAC.

  2. Modify the heartbeat properties.
    # geohb set-prop -p propertysetting \
    [-p…] heartbeatname
    -p propertysetting

    Specifies the default properties of the heartbeat.

    A heartbeat property is assigned a value by a name=statement pair. Multiple properties can be set at one time by using multiple statements.

    For more information about the properties you can set, see Appendix A, Standard Geographic Edition Properties.


    Specifies an identifier for the heartbeat settings.

    For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities.

    For more information about the geohb command, refer to the geohb(1M) man page.

Example 6-7 Modifying the Properties of the Default Heartbeat

This example modifies the settings for the default heartbeat between cluster-paris and cluster-newyork.

# geohb set-prop -p Query_interval=60 hb_cluster-paris~cluster-newyork