Time threshold in minutes beyond which the TDV server considers itself BLOCKED if it has not received a pending response.

60 minutes

1

The current global change ID is a counter for each change that occurs; it is the value displayed in brackets next to the status in Manager. This value matches across all nodes, although it might not match until changes are propagated. The IDs can differ by a maximum of one. Differences of 2 or more indicate a problem to investigate.

This is a read-only value that indicates the current server state.

-1

N/A

Copy Repository Database for Cluster Join

A mechanism used to speed up the performance of metadata replication by copying the TDV filesystem and repository artifacts. It is set to False by default and needs to be enabled when you first create a cluster.

Note:

False

N/A

After any node is flagged as down, specifies how often to check for the heartbeat of other nodes, in seconds.

300 seconds

1

(Optional Feature)

Health Monitor heartbeat table path in TDV. This configuration parameter must have a value specified for this optional feature to work.

The Cluster Health Monitor Table must be created using the Info tab for the data source where you want the heartbeat data cached. Using the Browse button leads you through a set of screens that you can use to have TDV create the table.

<null>

N/A

Number of seconds between heartbeats.

Frequency that the new Health Monitor table is updated with status.

600 seconds

1

Number of seconds to wait after sending a heartbeat before reading heartbeats of other nodes in cluster.

30 seconds

1

Number of seconds to wait after a node is unresponsive before flagging it as down.

600 seconds

1

Number of seconds between heartbeat messages the server sends out to other cluster members.

This is a read-only value that indicates the current cluster heartbeat interval. To change this value, use the Cluster Heartbeat Interval configuration parameter.

5 seconds

1

Number of seconds between heartbeat messages Server sends out to other cluster members.

Changing this value has no effect until the next server restart.

5 seconds

1 second

Can be set to:

OFF—No detailed logging is enabled.

MEMBER—Log member and timekeeper changes only.

METADATA—Log metadata changes in addition to member and timekeeper changes.

ALL—Log all cluster communications.

See the cs_server.log and cs_server_metadata.log in the <TDV_install_dir>\logs directory. See Configuring Logging for Active Cluster for information about other logging settings.

OFF

N/A

The minimum number of hours the server is to keep a metadata object after it is deleted. This is needed only if some servers in the cluster are not up all the time, or the network among the cluster members are intermittent. This setting is ignored if all servers in the cluster are running and communicating with each other.

72 hours

1

The time interval in seconds between attempts to contact a nonresponding remote cluster node.

5 seconds

0

The number of seconds the server is to wait for an initial response while establishing a connection to a remote cluster node.

5 seconds

0

Weight of time keeper

Set this if timekeeper needs special treatment in weighted round robin trigger distribution. For most use cases, this value does not need to be set.

1

0