It sounds like you're using Ignite in client / server mode, correct?
If so, then there is no script to shut the server instances down. Just killing the process should do (killing the server pids or closing the corresponding terminal window). And as far as the entire cluster, I don't believe there are any recommendations for a graceful shutdown beyond making sure the clients (Pega nodes) are brought down first. My understanding is that there will be changes in this area in 7.3.1, but I do not have anything specific I can share regarding this at this time.
yes, we are using ignite in client/server mode. Presently we are doing the exact same thing (killing/closing terminal) to kill the server instance for a particular node. But this process will not work in production (it's manual and we don't have access) so we would like to know if there is a better way of managing this process using some script or PEGA OOB way.
Also, coming to the entire cluster. we would like to know how to bring the entire cluster down after the clients (pega application nodes) were brought down.
Based on the information we received from PEGA, In 7.3.1 webcontainer deployment will be possible for ignite but not sure whether it has better process to manage the shutdown process.
Unfortunately In 7.3 there is no out of the box way to gracefully shutdown the Ignite server nodes, the same goes for the entire cluster. In 7.3.1 the Ignite servers are deployed as a WAR and can be managed in the same way as Pega nodes. Let us know if you have any other questions.