A host is an instance of MarkLogic Server. A host is not configured individually but as a member of a group. A host is added to the Default group if it is not joined to another group during the installation process. For example, in cases where MarkLogic is running in a single host environment, the host is added to the Default group.
Forests are created on hosts and added to a database to interact with HTTP, ODBC, and XDBC Servers running on the same or other hosts.
See the chapters Groups and Databases for more details on hosts as they relate to groups and databases.
A host is managed from both the Group and Hosts configuration screens. Use the following procedures to administer your hosts
This chapter describes how to use the Admin Interface to manage hosts. For details on how to manage hosts programmatically, see Host Maintenance Operations in the Scripting Administrative Tasks Guide.
This only applies for multi-host clusters. For information about installing MarkLogic and a more detailed procedure about joining a cluster, see the Installation Guide.
To add a host to a cluster, perform the following steps using the Admin Interface:
To change the group to which a host belongs, perform the following steps using the Admin Interface:
Changing the group to which a host belongs is a cold task; the server restarts to reflect the changes.
To shut down or to restart a host, perform the following steps:
The restart operation normally completes within a few seconds. It is possible, however, for it to take longer under some conditions (for example, if the Security database needs to run recovery or if the connectivity between hosts in a cluster is slow). If it takes longer than a few seconds for MarkLogic Server to restart, than the Admin Interface might return a 503: Service Unavailable
message. If you encounter this situation, wait several seconds and then reload the Admin Interface.
Clearing a forest on a host permanently deletes the data in the forest. The configuration information of the forest will be preserved. For example, you may want to clear the forest if you want to load new data into the same configuration.
To clear the data from a forest, perform the following steps using the Admin Interface:
Deleting a forest on a host permanently deletes the data in the forest as well as the configuration information. A forest cannot be deleted if it is still attached to a database. You must first detach the forest from the database before you can delete from a host.
Assuming that the forest is not attached to any database, perform the following steps to delete a forest from a host.
Deleting a host is a hot admin task for the other hosts in the group.
A host has to leave a cluster first to be moved to another cluster. Leaving a cluster is also a way to switch a host from a single host environment to a multi-host environment or vice versa. A host cannot leave a cluster if there are still forests assigned to it or if it has any foreign clusters associated with it; you must delete all forests assigned to the host and de-couple any clusters associated with a host before you can leave the cluster. In a single-host environment, a host cannot leave a cluster because it will always have forests assigned to it.
Perform the following steps to make a host leave a cluster:
In addition to the features that come standard in MarkLogic, there are optionally licensed features that you may want to take advantage of for more advanced projects.
To display the license options for a host, perform the following steps using the Admin Interface:
Option | Description |
---|---|
Advanced Geospatial | This License Option is required when using:
Other uses of Geospatial Search do not require Advanced Geospatial License Option. |
Advanced Security | This License Option is required when using: |
Semantics | This License Option is required to use Sparql features. Use of API's leveraging Semantics without Sparql, such as the SQL API, do not do not require a Semantics Option license. |
Flexible Replication | This License Option is required to use Flexible Replication. |
XA | This License Option is required to use XA. |
Tiered Storage | This License Option is required to use Tiered Storage. |
At any time, you can change the license key for a host from the Host Status page. You might need to change the license key if your license key expires, if you need to use some features that are not covered in your existing license key, if you upgrade your hardware with more CPUs and/or more cores, if you need a license that covers a larger database, if you require different languages, or for various other reasons. Changing the license key sometimes results in an automatic restart of MarkLogic (for example, if your new license enables a new language).
To change the license key for a host, perform the following steps using the Admin Interface:
Any optionally licensed features enabled by your license key appear in the License Key Options field.
Use Host Status page of the Admin Interface to rollback stalled or long-running transactions, discarding any updates made by the transaction. The Host Status page includes a list of transactions which have started but not yet completed.
To rollback the MarkLogic Server portion of a prepared XA transaction, see Rolling Back a Prepared XA Transaction Branch.
To rollback a transaction using the Admin Interface, complete the following steps:
http://yourhost:8001
.[rollback]
next to a transaction to initiate a transaction rollback. For example:There may be a slight delay between when a rollback is initiated and when the transaction terminates. During this period, the transaction still appears on the host status page, with a transaction status of awaiting rollback.