When you stop routing requests on Elasticsearch cluster nodes, you can perform corrective actions that might otherwise be difficult to complete. For example, if your cluster is being overwhelmed by requests because it is undersized for its workload, its nodes might not respond to efforts to resize. Think of this action as a maintenance mode for cluster nodes that can stop the cluster from becoming completely unresponsive, so that you can resolve operational issues much more effectively.
When you stop routing, no new requests are directed to the cluster node, but existing requests are permitted to be completed. Billing for the deployment does not change.
To stop routing on a cluster node:
- Log in to the Elasticsearch Add-On for Heroku console.
On the Deployments page, select your deployment.
Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
- Select Stop routing for one of the nodes. Repeat for additional nodes in the cluster, if necessary.
After your changes are complete, select Start routing to re-enable routing on the cluster.