Site Properties
The following table describes the site properties that the disaster recovery framework defines.
Table 11 Disaster Recovery Framework Site Properties
|
|
Description (string)
|
Describes the site. The system sets this property on the local cluster, then propagates the
value to the other clusters in the site.
Tuning recommendations: This property is assigned at
creation and tunable at runtime.
Category: Optional
Default: None
|
joinTimeout (integer)
|
Specifies, in seconds, the longest time that the JMX client, the site, waits for the
invocation of an MBean-server method to return. If a method does not return by the end of the
timeout period, the client moves to its next set of instructions and reports the operation as timed
out. By default, a client waits indefinitely for a method to return. If the MBean server is unable
to complete an invocation, the JMX client will hang indefinitely. The timeout period is site-wide
and applies to operations on a per-cluster basis.
The joinTimeout property is used when the join operation requires more time
to complete than the default setting allows before the geosite joincommand times
out.
Tuning recommendations: This property is assigned at
creation,but it is not tunable at runtime.
Category: Optional
Default: 30 seconds
Minimum: 20 seconds
Maximum: 3600 seconds
|
Query_interval (integer)
|
Specifies, in seconds, the frequency between heartbeat status requests used by the site
clusters. The plug-in enters emergency mode if three Query_interval periods pass
without response. The plug-in times out and enters error mode if a further
Query_interval period passes with no response.
Tuning recommendations: This property is assigned at
creation and tunable at runtime.
Category: Optional
Default: 120 seconds
Minimum: 20 seconds
Maximum: 300 seconds
|
Timeout (integer)
|
Specifies, in seconds, the longest time that the JMX client, the site, waits for the
invocation of an MBean-server method to return. If a method does not return by the end of the
timeout period, the client moves to its next set of instructions and reports the operation as timed
out. By default, a client waits indefinitely for a method to return. If the MBean server is unable
to complete an invocation, the JMX client will hang indefinitely. The timeout period is site-wide
and applies to operations on a per-cluster basis.
Tuning recommendations: This property is assigned at
creation and tunable at runtime.
Category: Optional
Default: 30 seconds
Minimum: 30 seconds
Maximum: 3600 seconds
|
|