You can restart your SearchStax Cloud Dedicated demplyments in three ways:
Rolling Restart of Cluster
A “rolling restart” of a SearchStax Cloud cluster is harmless (no service down time) and often has a beneficial effect on the speed and throughput of the cluster. Look on the Deployment Details page (where the HTTP Solr Endpoint is shown).
Click the Restart All Solr Nodes button. SearchStax will stop one Solr node at a time, and will wait until that node is on-line before stopping the next one.
In some circumstances, your attempt to launch a rolling restart will produce this message:
This means that a replica or a node is down, and restarting the remaining node(s) could cause a service outage. Contact the SearchStax Support Desk for assistance.
Individual Node Restart
The SearchStax Cloud Dashboard offers links to help you start and stop individual Solr instances. Look on the Deployment Details page (where the HTTP Solr Endpoint is shown).
In some situations, it may not be possible to restart the node from this link. If you encounter any difficulty, contact SearchStax Support and we’ll take care of it.
Restart from API
The SearchStax Cloud Deployment API offers a RESTful API for managing Solr nodes. Please see:
- account > deployment > rolling_restart. This method will trigger a rolling restart not only of Solr nodes but of Zookeeper nodes, too.
- account > deployment > server > start_solr
- account > deployment > server > stop_solr
Questions?
Do not hesitate to contact the SearchStax Support Desk.