In the following sections, typical administrative tasks relating to the management of a GraphDB-Enterprise cluster instance are covered.
After the instantiation of a master node, worker nodes can be added using a JMX client application, e.g. jconsole. From the MBeans tab, select the bean associated with the master node to be modified. Each bean will be named: ReplicationCluster/ClusterInfo/<repository_id>.
Worker nodes can be added using the addClusterNode operation, with the following parameters:
Worker nodes are removed using the removeClusterNode operation, which requires only the repository URL.
If a master node is assigned two worker nodes of unknown, but different, status, then it will not be able to decide which of the nodes is correct. In this situation, both workers should be removed, the master's transaction log cleared, and the workers added back with the 'correct' worker first.
If a master node fails completely, then the clients of the repository will start getting errors when trying to query or update the repository. In order to avoid this, use at least one additional master and the Client Failover API.
The Status attribute of the master mode indicates the cluster health according to the table:
Table: Description of possible values of the Status attribute.
The master node automatically initiates replication of worker nodes as needed or appropriate. The manual replication option is obsolete and no longer available.
Cluster-wide backup and restore can be used to restore the cluster back to a previous operational state.
Backups are made by copying a worker node's image to a location on the master node's machine. Restoring an image is made from a local image on the master node and replicated throughout worker nodes in the cluster, propagating via peer master nodes as needed.
To start a backup, invoke the backup operation with a single parameter, the name used to identify the image. The backup image will go into a directory under the master node's repository data directory. At least two notification messages will be sent under normal operation, one to indicate that the backup operation has been started, and another to indicate that it has completed successfully.
To restore the cluster state from a backup image, invoke the restoreFromImage operation with an existing backup's name as a parameter. The image created by the backup will be replicated to every worker throughout the cluster. At least two notification messages will be sent under normal operation, one to indicate that the restore operation has been started, and another to indicate that it has completed successfully.
Important usage notes:
Remote replication is no longer available.
Skip to end of metadata Go to start of metadata