System-Defined Properties in the RTR File

The following listing shows the system-defined properties in the sample RTR file.

# A list of bracketed resource property declarations follows the 
# resource-type declarations. The property-name declaration must
be
# the first attribute after the open curly bracket of each entry.
#

# The <method>_timeout properties set the value in seconds
after which 
# the RGM concludes invocation of the method has failed. 

# The MIN value for all method timeouts is set to 60 seconds. This 
# prevents administrators from setting shorter timeouts, which do
not 
# improve switchover/failover performance, and can lead to undesired 
# RGM actions (false failovers, node reboot, or moving the resource
group 
# to ERROR_STOP_FAILED state, requiring operator intervention).
Setting
# too-short method timeouts leads to a *decrease* in overall availability 
# of the data service.
{  
	PROPERTY = Start_timeout; 
	MIN=60; 
	DEFAULT=300;
}

{
	PROPERTY = Stop_timeout; 
	MIN=60; 
	DEFAULT=300;
}
{
        PROPERTY = Validate_timeout;
        MIN=60;
        DEFAULT=300;
}
{
        PROPERTY = Update_timeout;
        MIN=60;
        DEFAULT=300;
}
{
        PROPERTY = Monitor_Start_timeout;
        MIN=60;
        DEFAULT=300;
}
{
        PROPERTY = Monitor_Stop_timeout;
        MIN=60;
        DEFAULT=300;
}
{
        PROPERTY = Thorough_Probe_Interval;
        MIN=1;
        MAX=3600;
        DEFAULT=60;
        TUNABLE = ANYTIME;
}

# The number of retries to be done within a certain period before
concluding 
# that the application cannot be successfully started on this node.
{
        PROPERTY = Retry_Count;
        MIN=0;
        MAX=10;
        DEFAULT=2;
        TUNABLE = ANYTIME; 
}

# Set Retry_Interval as a multiple of 60 since it is converted from
seconds
# to minutes, rounding up. For example, a value of 50 (seconds)
# is converted to 1 minute. Use this property to time the number
of 
# retries (Retry_Count).
{
        PROPERTY = Retry_Interval;
        MIN=60;
        MAX=3600;
        DEFAULT=300;
        TUNABLE = ANYTIME;
}

{
        PROPERTY = Network_resources_used;
        TUNABLE = AT_CREATION;
        DEFAULT = "";
}

Although Sun Cluster provides the system-defined properties, you can set different default values using resource property attributes. See "Resource Property Attributes" for a complete list of attributes available for applying to resource properties.

Note the following about the system-defined resource properties in the sample RTR file:

• Sun Cluster provides a minimum value (1 second) and a default value (3600 seconds) for all timeouts. The sample RTR file changes the minimum 60 and changes the default to 300 seconds. A cluster administrator can accept this default value or change the value of the timeout to something else, (60 or greater). Sun Cluster has no maximum allowable value.

• The properties Thorough_Probe_Interval, Retry_count, and Retry_interval, have the TUNABLE attribute set to ANYTIME. This settings means the cluster administrator can change the value of these properties, even when the data service is running. These properties are used by the fault monitor implemented by the sample data service. The sample data service implements an UPDATE method to stop and restart the fault monitor when these or other resource properties are changed by administrative action. See "UPDATE Method".

• Resource properties are classified as

  • required--the cluster administrator must specify a value when creating a resource;

  • optional--if the administrator does not specify a value, the system supplies a default value.

  • conditional--the RGM creates the property only if it is declared in the RTR file.

  The fault monitor of the sample data service makes use of the Thorough_probe_interval, Retry_count, Retry_interval, and Network_resources_used conditional properties, so the developer needed to declare them in the RTR file. See the r_properties(5) man page or "Resource Properties" for information about how properties are classified.