Shutting down IBM Safer Payments

A shut down might be needed if an instance is deadlocked or stuck. A shutdown must complete so that data is not lost.

Normal shutdown

Complete a normal shutdown by using the API, kill -15 <iris_pid>, or kill <iris_pid>.

During a normal shutdown, data is not lost. Wait at least one hour if the instance does not shut down. If the instance did not shut down within one hour, run the gdb commands. Analyze the backtrace and find the reason why.

gdb -p `pidof iris`
set height 0
set logging on
thread apply all bt
quit

The shutdown can take up to 90 minutes for larger configurations with deferred writing enabled.

Hard shutdown

Complete a hard shutdown by using kill -8 <iris_pid> (run command twice). A hard shutdown can result in data loss, and a restore might be necessary afterward.

Pending transactions and running tasks might be canceled but try to write data to disk. Also, a backtrace is printed to the log folder in releases 5.5.0.3 and higher. This process can take several minutes. Check for data loss or potential errors after startup. Wait at least 10 minutes. If the instance did not shutdown, complete an immediate shutdown.

Immediate shutdown

Complete an immediate shutdown by using kill -9 <iris_pid>.

Sockets and files are immediately closed without writing. It might cause some data loss and some indexes might break, in which case it is best to set the iris.iris file to Invalidated and restore the killed instance.