Clusters: Configuration: Migration

If a clustered server fails, Node Manager can automatically restart the server and its services on another machine. This page allows you to specify the machines where Node Manager can restart migratable servers and to specify the data source used during server migration.

Name	Description
Candidate Machines For Migratable Servers	The set of machines (and order of preference) on which Node Manager will restart failed servers. (Requires you to enable each server for automatic migration.) Each server can specify a subset of these cluster-wide candidates, which limits the machines on which the server can be restarted. Servers can also specify their own order of preference. MBean Attribute: `ClusterMBean.CandidateMachinesForMigratableServers` Changes take effect after you redeploy the module or restart the server.
Migration Basis	Controls the mechanism used for server migration. MBean Attribute: `ClusterMBean.MigrationBasis` Changes take effect after you redeploy the module or restart the server.
Data Source For Automatic Migration	The data source used by servers in the cluster during migration. (You must configure each Migratable Server within the cluster to use this data source.) MBean Attribute: `ClusterMBean.DataSourceForAutomaticMigration` Changes take effect after you redeploy the module or restart the server.
Auto Migration Table Name	Return the name of the table to be used for server migration. MBean Attribute: `ClusterMBean.AutoMigrationTableName` Changes take effect after you redeploy the module or restart the server.
Member Discovery Timeout	Gets the MemberDiscoveryTimeout value. This value defines the amount of time a server waits during or after startup to discover members that belong to the same cluster. This information is used to join or form a new cluster. MBean Attribute: `DatabaseLessLeasingBasisMBean.MemberDiscoveryTimeout` Minimum value: `10` Changes take effect after you redeploy the module or restart the server.
Leader Heartbeat Period	Gets the LeaderHeartbeatPeriod value. The cluster leader heartbeats a special leader heartbeat every period seconds to publish group view version and other cluster information. Members look at this heartbeat and perform any sync up operations if required. Minimum value: `1` Changes take effect after you redeploy the module or restart the server.

Administration Console Online Help

Clusters: Configuration: Migration

Configuration Options