UTM cluster applications involve application data that is valid globally throughout the cluster as well as application data that is specific to the node:
Application data that is valid globally throughout the cluster includes GSSB, ULS and the service data of non-node-bound services. This data is present in the UTM cluster files.
Data that is applicable locally at node level such as, for example, TLS and the service data of node-bound services (see "Service restart") is saved in the KDCFILE of the relevant node application.
The abnormal termination of a node application has the following consequences for the application data:
Any locks that were set for the cluster's global ULS and GSSB storage areas at the time the node application terminated are retained.
Any users who were signed on exclusively at the node application at that time continue to be signed on.
It is not possible to access the service data of users who were signed on at the node application at the time of the failure until such a warm start is performed.
The pages in the cluster page pool that were reserved by the abnormally terminated node application continue to be occupied.
No node updates, cluster updates or online imports are possible.
Therefore, a warm start should rapidly be performed for abnormally terminated node applications.