This chapter describes some of the basic configuration tasks for a cluster. When you have a cluster, you can perform most administrative tasks from the Admin Interface of any node in the cluster. This chapter describes some of those cluster tasks and includes the following sections:
The Admin Interface has summary and status screens to help you determine the makeup of a cluster. The system summary page (the default Admin Interface page when you log in) has links to each group and to each host in the cluster. If you have a cluster with multiple groups configured and you click on a group, the Admin Interface displays a group summary page which shows all of the hosts in a group. For each group, there is also a status page.
Similarly, each host has a summary page and a status page. For more details about the status pages, see Monitoring MarkLogic Server Performance in the Query Performance and Tuning Guide book.
This section describes the general procedure for adding a new node to an existing cluster. For more detailed installation instructions, including the procedure to add a new node to a cluster, see the Installation Guide.
The following are the general steps needed to add another node to an existing cluster (the existing cluster can have one or more hosts):
raymond
, access http://raymond:8001
.Accepting this license agreement is optional. However, to begin using MarkLogic Server, you must accept the terms and conditions outlined in the license agreement. If you have executed a written software license with MarkLogic Corporation, the agreement displayed references that written agreement.
If you want to remove a node from a cluster, you must log into the Admin Interface for that node, go to its host configuration page and click the leave
button.
Before you remove a node from a cluster, make sure it is not hosting any forests for the cluster (the forest summary page shows this information) or is not acting as a failover host for any forests. Additionally, make sure it is not coupled to any other hosts as a foreign cluster. You must resolve any forest dependencies with other hosts and de-couple any foreign clusters before you can remove a host from the cluster; the Admin Interface will not allow you to remove a host from the cluster if there are other hosts depending on it, and it will attempt to help you to resolve the dependencies. That might involve removing the host as a failover host, detaching the forest from the database, or assigning the forest to another d-node. For details about managing forests, see the Administrator's Guide.
Perform the following basic procedure to remove a host from a cluster:
leave
button. The leave
button only appears when you are using the Admin Interface on which the host machine is running. On the Admin Interface on other nodes in the cluster, there is an admin
button, which is a link to open the Admin Interface running on that host.At this point, the installation process will begin again (although you will not have to reenter the license key information). You can choose to join the cluster again, join another cluster, or skip the cluster installation and install as a stand-alone host.
Each host in a MarkLogic cluster must run the same version of the MarkLogic software. Therefore, if you install a maintenance release, you need to install it on all of the hosts in the cluster.
For clusters upgraded from MarkLogic 8 or older, the Security forests and the schemas forests must be on the same host, and that host should be the first host you upgrade when upgrading a cluster. If two clusters are using database replication to replicate the security database, see the procedure described in Upgrading from Release 9.0-1 or Later in the Installation Guide. Starting with MarkLogic 9, Security databases are created without a triggers database and without a schemas database.
If you are using database replication in your cluster, see Upgrading Clusters Configured with Database Replication in the Database Replication Guide.
The upgrade installation is relatively quick, and should require only a small amount of cluster down time. It does require each host to shut down, uninstall, reinstall, and start up, however.
For a more detailed upgrade procedure, see the Installation Guide. The general procedure for upgrading a cluster is as follows:
rpm -e MarkLogic
on Red Hat Linux, and with pkgrm MARKlogic
on Solaris). For details, see the Installation Guide.rpm -i
on Red Hat Linux, pkgadd MARKlogic
on Solaris). For details, see the Installation Guide.When the Admin Interface returns, this concludes the upgrade, and the upgraded cluster is now available to accept requests.