Editing Cluster Operations (section)

=== Follow Through ===
When doing any activity that disrupts the cluster operations enough to cause it to drop into a "YELLOW" or "RED" state, wait until the cluster is "GREEN" again before proceeding.  In the case of a full rolling restart (one node at a time), the cluster should be "GREEN" before proceeding to the next node.

This process (node rolling restart, anyway) is captured in the script <code>node-restart.sh</code>:
 #!/bin/bash
 #
 # perform a soft restart of a node, minimizing the reindexing that would
 #  normally occur when a node drops/inserts
 
 # set to one of the master nodes
 MASTER=master-node
 
 # replace with either the real admin password or a cert/key combination
 AUTH="-u admin:admin"
 
 # first shut off shard allocation
 curl -XPUT -H "Content-Type: application/json" <nowiki>https://$MASTER:9200/_cluster/settings</nowiki> $AUTH -d '
 {
   "persistent": {
     "cluster.routing.allocation.enable": "primaries"
   }
 }'
 echo
 
 # now flush the cache
 curl -XPOST <nowiki>https://$MASTER:9200/_flush</nowiki> $AUTH
 echo
 
 # restart the opensearch process
 sudo systemctl restart opensearch
 
 # re-enable shard allocation
 curl -XPUT -H "Content-Type: application/json" <nowiki>https://$MASTER:9200/_cluster/settings</nowiki> $AUTH -d '
 {
   "persistent": {
     "cluster.routing.allocation.enable": null
   }
 }'
 echo
This script is intended to be run on the node being restarted.