Appendix A: ‘Hot’ versus ‘Cold’ Admin Tasks
“Hot” admin tasks are defined as tasks that take effect immediately and do not require the server to restart. “Cold” admin tasks are defined as tasks that require one or more instances of the server to restart to reflect the changes. Cold tasks have an asterisk (*) next to the setting in the Admin Interface.
In a clustered deployment, “cold” tasks will require one or more hosts in the cluster to restart their instance of MarkLogic in order to reflect the changes. In an single-server deployments, “cold” tasks will cause MarkLogic to restart in order to reflect the changes.
This section shows the “hot” or “cold” status for adding objects, changing configuration parameters, and dropping objects.